Re: GiST insert algorithm rewrite - Mailing list pgsql-hackers

From Greg Stark
Subject Re: GiST insert algorithm rewrite
Date
Msg-id AANLkTikifgfxK6j70LJEgKHyHz-k6cWyQ3pkxhQaugAq@mail.gmail.com
Whole thread Raw
In response to Re: GiST insert algorithm rewrite  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: GiST insert algorithm rewrite  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
List pgsql-hackers
On Mon, Dec 13, 2010 at 3:14 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> I think you need to refactor the operation so that there's one WAL
> record per child page, or something along that line.  I concede this
> might be diffcult :-(

If it's only the backup blocks that matter couldn't you generate noop
WAL records with just the full page image in them. Once all those are
generated then generate the actual split operation and since all the
pages have been written to wal since the last checkpoint they won't
need any backup block slots.

This would require surpressing any checkpoints between writing the
first backup block and the final operation record. That might be
pretty hard to do cleanly.


--
greg


pgsql-hackers by date:

Previous
From: "BRUSSER Michael"
Date:
Subject: Re: initdb failure with Postgres 8.4.4
Next
From: Andrew Dunstan
Date:
Subject: Re: initdb failure with Postgres 8.4.4