Re: CompactCheckpointerRequestQueue versus pad bytes
Robert Haas <robertmhaas@gmail.com>
From: Robert Haas <robertmhaas@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-hackers@postgresql.org
Date: 2012-07-17T00:35:46Z
Lists: pgsql-hackers
On Mon, Jul 16, 2012 at 7:17 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote: > The attached patch covers everything discussed in this thread, except > for the buggy handling of stats, which I think should be fixed in a > separate patch since it's only relevant to 9.2+. With respect to this chunk: + * We do not need to go through this dance for temp relations, though, because + * we never make WAL entries for temp rels, and so a temp rel poses no threat + * to the health of a regular rel that has taken over its relfilenode number. ...I would say that a clearer way to put this is that temporary relations use a different file naming convention than permanent relations and therefore there can never be any confusion between the two. Other than that, looks fine to me. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Include the backend ID in the relpath of temporary relations.
- debcec7dc31a 9.1.0 cited