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-02T14:30:14Z
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:
> I think we can fix this by requiring that any multi-WAL-record actions 
> that are in-progress when a checkpoint starts (at the REDO-pointer) must 
> finish before the checkpoint record is written.

What happens if someone wants to start a new split while the checkpoint
is hanging fire?

			regards, tom lane