Re: [PATCH 04/16] Add embedded list interface (header only)
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andres Freund <andres@2ndquadrant.com>
Cc: pgsql-hackers@postgresql.org, Peter Geoghegan <peter@2ndquadrant.com>, Robert Haas <robertmhaas@gmail.com>
Date: 2012-06-25T15:57:51Z
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 →
-
Don't waste the last segment of each 4GB logical log file.
- dfda6ebaec67 9.3.0 cited
-
Stamp HEAD as 9.3devel.
- bed88fceac04 9.3.0 cited
-
Wake WALSender to reduce data loss at failover for async commit.
- 2c8a4e9be273 9.2.0 cited
-
Make the visibility map crash-safe.
- 503c7305a1e3 9.2.0 cited
Andres Freund <andres@2ndquadrant.com> writes: > On Monday, June 25, 2012 05:15:43 PM Tom Lane wrote: >> So you propose to define any compiler that strictly implements C99 as >> not sensible and not one that will be able to compile Postgres? > I propose to treat any compiler which has no way to get to equivalent > behaviour as not sensible. Yes. Well, my response is "no". I could see saying that we require (some) C99 features at this point, but not features that are in no standard, no matter how popular gcc might be. > I don't think there really are many of those > around. As you pointed out there is only one compiler in the buildfarm with > problems This just means we don't have a wide enough collection of non-mainstream machines in the buildfarm. Deciding to break any platform with a non-gcc-equivalent compiler isn't going to improve that. regards, tom lane