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

From David Steele
Subject PATCH: Exclude additional directories in pg_basebackup
Date
Msg-id ced3b05f-c1d9-c262-ce63-9744ef7e6de8@pgmasters.net
Whole thread Raw
Responses Re: PATCH: Exclude additional directories in pg_basebackup  (Stephen Frost <sfrost@snowman.net>)
Re: PATCH: Exclude additional directories in pg_basebackup  (Jim Nasby <Jim.Nasby@BlueTreble.com>)
Re: PATCH: Exclude additional directories in pg_basebackup  (Robert Haas <robertmhaas@gmail.com>)
Re: PATCH: Exclude additional directories in pg_basebackup  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
List pgsql-hackers
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.

The attached patch adds these directories to the pg_basebackup
exclusions and takes an array-based approach to excluding directories
and files during backup.

I also incorporated Ashutosh's patch to fix corruption when
pg_stat_tmp/pg_replslot are links [1].  This logic has been extended to
all excluded directories.

Perhaps these patches should be merged in the CF but first I'd like to
see if anyone can identify problems with the additional exclusions.

Thanks,
--
-David
david@pgmasters.net

[1]
http://www.postgresql.org/message-id/flat/CAE9k0Pm7=x_o0W7E2b2s2cWcZdcBGczGdrxttzXOZGp8bEBcGw@mail.gmail.com/

Attachment

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Let's get rid of the separate minor version numbers for shlibs
Next
From: Stephen Frost
Date:
Subject: Re: PATCH: Exclude additional directories in pg_basebackup