Re: Allow wal_keep_segments to keep all segments

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>
Cc: Bruce Momjian <bruce(at)momjian(dot)us>, Simon Riggs <simon(at)2ndQuadrant(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Josh Berkus <josh(at)agliodbs(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Allow wal_keep_segments to keep all segments
Date: 2010-06-03 21:31:54
Message-ID: 4C081F4A.1010204@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Heikki Linnakangas wrote:
>
> We leave that up to the DBA to clean out one way or another. We
> provide restartpoint_command and the %r option in restore_command to
> help with that.
>
>

I was in fact just looking into this, and I see that there is no example
restartpoint_comand script given in the docs, nor in the wiki.

A sample of such a command would be useful. This is all going to feel a
bit strange to lots of users, and the more we can hold their hands the
better off we and they will be.

cheers

andrew

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Greg Stark 2010-06-03 21:58:19 Re: Exposing the Xact commit order to the user
Previous Message Tom Lane 2010-06-03 21:11:30 Re: clarification on walsender protocol document