Re: PATCH: Exclude additional directories in pg_basebackup - Mailing list pgsql-hackers

From Robert Haas
Subject Re: PATCH: Exclude additional directories in pg_basebackup
Date
Msg-id CA+TgmoYM6EqMk02KVkJwfy+0EjVVdvgZZgOVtP=L7Rq2km3g1A@mail.gmail.com
Whole thread Raw
In response to PATCH: Exclude additional directories in pg_basebackup  (David Steele <david@pgmasters.net>)
Responses Re: PATCH: Exclude additional directories in pg_basebackup  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Re: PATCH: Exclude additional directories in pg_basebackup  (David Steele <david@pgmasters.net>)
List pgsql-hackers
On Mon, Aug 15, 2016 at 3:39 PM, David Steele <david@pgmasters.net> wrote:
> Recently a hacker proposed a patch to add pg_dynshmem to the list of
> directories whose contents are excluded in pg_basebackup.  I wasn't able
> to find the original email despite several attempts.
>
> That patch got me thinking about what else could be excluded and after
> some investigation I found the following: pg_notify, pg_serial,
> pg_snapshots, pg_subtrans.  These directories are all cleaned, zeroed,
> or rebuilt on server start.

Eh ... I doubt very much that it's safe to blow away the entire
contents of an SLRU between shutdown and startup, even if the data is
technically transient data that won't be needed again after the system
is reset.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Are these supported??
Next
From: Andrew Gierth
Date:
Subject: Re: [GENERAL] C++ port of Postgres