Prev: pg_dump's checkSeek() seems inadequate
Next: suppress automatic recovery after back crash
From: Robert Haas on 27 Jun 2010 20:54
[moving from -performance to -hackers; original subject is: PostgreSQL
as a local in-memory cache]

On Thu, Jun 17, 2010 at 7:25 PM, Tom Lane <tgl(a)sss.pgh.pa.us> wrote:
> Josh Berkus <josh(a)agliodbs.com> writes:
>>> (a) and (d) are probably simple, if by "reprovisioning" you mean
>>> "rm -rf $PGDATA; initdb".
>
>> Exactly.  Followed by "scp database_image".  Or heck, just replacing the
>> whole VM.
>
> Right, that would work.  I don't think you really need to implement that
> inside Postgres.  I would envision having the startup script do it, ie
>
>        rm -rf $PGDATA
>        cp -pr prepared-database-image $PGDATA
>
>        # this loop exits when postmaster exits normally
>        while ! postmaster ...
>        do
>                rm -rf $PGDATA
>                cp -pr prepared-database-image $PGDATA
>        done
>
> Then all you need is a tweak to make the postmaster exit(1) after
> a crash instead of trying to launch recovery.

This seems useful to me so here's a patch to implement it.

There didn't seem to be a suitable GUC category for it, until I
noticed that we have a currently-undocumented GUC called
exit_on_error. I thought it might make sense to document both that
and this in a new section called "Error Handling".

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company
 | 
Pages: 1
Prev: pg_dump's checkSeek() seems inadequate
Next: suppress automatic recovery after back crash