[COMMITTERS] pgsql: Include previous TLI in end-of-recovery and shutdown checkpoint

2013-02-11 Thread Heikki Linnakangas
Include previous TLI in end-of-recovery and shutdown checkpoint records. This isn't used for anything but a sanity check at the moment, but it could be highly valuable for debugging purposes. It could also be used to recreate timeline history by traversing WAL, which seems useful. Branch -- m

Re: [COMMITTERS] pgsql: Include previous TLI in end-of-recovery and shutdown checkpoint

2013-02-11 Thread Tom Lane
Heikki Linnakangas writes: > Include previous TLI in end-of-recovery and shutdown checkpoint records. Hm ... should this patch have included a WAL format version bump (XLOG_PAGE_MAGIC)? It may not matter too much, since we already have a different value from 9.2 there. r

Re: [COMMITTERS] pgsql: Include previous TLI in end-of-recovery and shutdown checkpoint

2013-02-11 Thread Tom Lane
Heikki Linnakangas writes: > On 11.02.2013 18:28, Tom Lane wrote: >> Hm ... should this patch have included a WAL format version bump >> (XLOG_PAGE_MAGIC)? > I bumped PG_CONTROL_VERSION, that forces an initdb too. Right, but that data isn't so easily available to WAL-stream consumers.

[COMMITTERS] pgsql: Fix checkpoint after fast promotion.

2013-02-11 Thread Heikki Linnakangas
Fix checkpoint after fast promotion. The intention was to request a regular online checkpoint immediately after end of recovery, when performing "fast promotion". However, because the checkpoint was requested before other backends were allowed to write WAL, the checkpointer process performed a res

[COMMITTERS] pgsql: Support unlogged GiST index.

2013-02-11 Thread Heikki Linnakangas
Support unlogged GiST index. The reason this wasn't supported before was that GiST indexes need an increasing sequence to detect concurrent page-splits. In a regular WAL- logged GiST index, the LSN of the page-split record is used for that purpose, and in a temporary index, we can get away with a