Horton

Re: B-tree parent pointer and checkpoints

Tom Lane <tgl@sss.pgh.pa.us>

View thread
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2010-11-10T22:26:17Z
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 →

  1. Rewrite the GiST insertion logic so that we don't need the post-recovery

Heikki Linnakangas <heikki.linnakangas@enterprisedb.com> writes:
> The new rule is that before you start a multi-WAL-record operation that 
> needs to be completed at end of recovery if you crash in the middle, you 
> call HoldCheckpoint(), and once you're finished, ResumeCheckpoint(). 

What happens if you error out in between?  Or is it assumed that the
*entire* sequence is a critical section?  If it has to be that way,
one might wonder what's the point of trying to split it into multiple
WAL records.

			regards, tom lane