Re: narwhal and PGDLLIMPORT
Andres Freund <andres@2ndquadrant.com>
From: Andres Freund <andres@2ndquadrant.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Amit Kapila <amit.kapila16@gmail.com>,
pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2014-02-04T09:25:22Z
Lists: pgsql-hackers
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
MinGW: Link with shell32.dll instead of shfolder.dll.
- 53566fc0940c 9.5.0 cited
-
Centralize getopt-related declarations in a new header file pg_getopt.h.
- 60ff2fdd9970 9.4.0 cited
-
Get rid of use of dlltool in Mingw builds.
- 846e91e0223c 9.4.0 cited
-
Export a few more symbols required for test_shm_mq module.
- 7d7eee8bb702 9.4.0 cited
-
Export set_latch_on_sigusr1 symbol for Windows.
- 708c529c7fde 9.4.0 cited
-
Use SHGetFolderPath instead of SHGetSpecialFolderPath to find the
- 889f03812916 8.1.0 cited
On 2014-02-04 02:10:47 -0500, Tom Lane wrote: > Amit Kapila <amit.kapila16@gmail.com> writes: > > In the function where it is used, it seems to me that it is setting DateStyle > > as ISO if it is not ISO and function configure_remote_session() will set it > > to ISO initially. So basically even if the value of DateStyle is junk, it will > > just do what we wanted i.e setting it to ISO. Does the failure is due to reason > > that it is not expecting DateStyle to be ISO and due to junk value of this > > parameter it sets the same to ISO. > > Meh. It might be that the DateStyle usage in postgres_fdw would > accidentally fail to malfunction if it saw a bogus value of the variable. > But it's hard to believe that this would be true of MainLWLockArray. There's not that much lwlock usage in contrib. It's just pg_stat_statements and pg_buffercache. Neither has tests... So it very well could be that breakage simply hasn't been observed. Greetings, Andres Freund -- Andres Freund http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services