Re: CompactCheckpointerRequestQueue versus pad bytes
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Robert Haas <robertmhaas@gmail.com>
Cc: pgsql-hackers@postgresql.org
Date: 2012-07-17T18:01:10Z
Lists: pgsql-hackers
I wrote: > I had thought that we might get a performance boost here by saving fsync > queue traffic, but I see that md.c was already not calling > register_dirty_segment for temp rels, so there's no joy there. Actually, wait a second. We were smart enough to not send fsync requests in the first place for temp rels. But we were not smart enough to not call ForgetRelationFsyncRequests when deleting a temp rel, which made for an entirely useless scan through the pending-fsyncs table. So there could be win there, on top of not forwarding the actual unlink operation. regards, tom lane
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