Re: PATCH: Exclude additional directories in pg_basebackup

From: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
To: David Steele <david(at)pgmasters(dot)net>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
Cc: Pg Hackers <pgsql-hackers(at)postgresql(dot)org>, Ashutosh Sharma <ashu(dot)coek88(at)gmail(dot)com>
Subject: Re: PATCH: Exclude additional directories in pg_basebackup
Date: 2016-09-12 18:50:52
Message-ID: ffbbf58a-9463-2cae-43b6-9ea7e2851b4a@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

The comments on excludeDirContents are somewhat imprecise. For
example, none of those directories are actually removed or recreated
on startup, only the contents are.

The comment for pg_replslot is incorrect. I think you can copy
replication slots just fine, but you usually don't want to.

What is the 2 for in this code?

if (strcmp(pathbuf + 2, excludeFile[excludeIdx]) == 0)

I would keep the signature of _tarWriteDir() similar to
_tarWriteHeader(). So don't pass sizeonly in there, or do pass in
sizeonly but do the same with _tarWriteHeader().

The documentation in pg_basebackup.sgml and protocol.sgml should be
updated.

Add some tests. At least test that one entry from the directory list
and one entry from the files list is not contained in the backup
result. Testing the symlink handling would also be good. (The
pg_basebackup tests claim that Windows doesn't support symlinks and
therefore skip all the symlink tests. That seems a bit at odds with
your code handling symlinks on Windows.)

--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Heikki Linnakangas 2016-09-12 19:07:40 Re: Tuplesort merge pre-reading
Previous Message Andres Freund 2016-09-12 18:18:11 Re: Implement targetlist SRFs using ROWS FROM() (was Changed SRF in targetlist handling)