From: | Josh Kupershmidt <schmiddy(at)gmail(dot)com> |
---|---|
To: | Gurjeet Singh <gurjeet(at)singh(dot)im> |
Cc: | PGSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Proposing pg_hibernate |
Date: | 2014-05-30 21:33:26 |
Message-ID: | CAK3UJRGKOzx_pO+QESNKncHRVZeaNfeueJDM+L41aKcKNogPqw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, May 27, 2014 at 10:01 PM, Gurjeet Singh <gurjeet(at)singh(dot)im> wrote:
> When the Postgres server is being stopped/shut down, the `Buffer
> Saver` scans the
> shared-buffers of Postgres, and stores the unique block identifiers of
> each cached
> block to the disk. This information is saved under the `$PGDATA/pg_hibernator/`
> directory. For each of the database whose blocks are resident in shared buffers,
> one file is created; for eg.: `$PGDATA/pg_hibernator/2.postgres.save`.
This file-naming convention seems a bit fragile. For example, on my
filesystem (HFS) if I create a database named "foo / bar", I'll get a
complaint like:
ERROR: could not open "pg_hibernator/5.foo / bar.save": No such file
or directory
during shutdown.
Josh
From | Date | Subject | |
---|---|---|---|
Next Message | Jeff Janes | 2014-05-30 22:21:24 | Re: recovery testing for beta |
Previous Message | Tom Lane | 2014-05-30 20:31:57 | Re: [HACKERS] unable to build postgres-9.4 in os x 10.9 with python |