Re: PostgreSQL as a local in-memory cache - Mailing list pgsql-performance

From Tom Lane
Subject Re: PostgreSQL as a local in-memory cache
Date
Msg-id 28137.1276817111@sss.pgh.pa.us
Whole thread Raw
In response to Re: PostgreSQL as a local in-memory cache  (Josh Berkus <josh@agliodbs.com>)
List pgsql-performance
Josh Berkus <josh@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.

            regards, tom lane

pgsql-performance by date:

Previous
From: Tom Lane
Date:
Subject: Re: Add slowdown after conversion to UTF8
Next
From: Tom Wilcox
Date:
Subject: Re: requested shared memory size overflows size_t