Re: [HACKERS] Exclude pg_internal.init from base backup - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: [HACKERS] Exclude pg_internal.init from base backup
Date
Msg-id CANP8+jJtQrdiZUnkykKDhxnzAjNQnxEb2_HxqpSt+0SNPB1sfA@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] Exclude pg_internal.init from base backup  (Magnus Hagander <magnus@hagander.net>)
Responses Re: [HACKERS] Exclude pg_internal.init from base backup
List pgsql-hackers
On 5 November 2017 at 11:55, Magnus Hagander <magnus@hagander.net> wrote:
> On Sat, Nov 4, 2017 at 4:04 AM, Michael Paquier <michael.paquier@gmail.com>
> wrote:
>>
>> On Fri, Nov 3, 2017 at 4:04 PM, Petr Jelinek
>> <petr.jelinek@2ndquadrant.com> wrote:
>> > Not specific problem to this patch, but I wonder if it should be made
>> > more clear that those files (there are couple above of what you added)
>> > are skipped no matter which directory they reside in.
>>
>> Agreed, it is a good idea to tell in the docs how this behaves. We
>> could always change things so as the comparison is based on the full
>> path like what is done for pg_control, but that does not seem worth
>> complicating the code.
>
>
> pg_internal.init can, and do, appear in multiple different directories.
> pg_control is always in the same place. So they're not the same thing.
>
> So +1 for documenting the difference in how these are handled, as this is
> important to know for somebody writing an external tool for it.

Changes made, moving to commit the attached patch.

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

-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

Attachment

pgsql-hackers by date:

Previous
From: Fabrízio de Royes Mello
Date:
Subject: Re: [HACKERS] Additional logging for VACUUM and ANALYZE
Next
From: Geoff Winkless
Date:
Subject: Re: [HACKERS] MERGE SQL Statement for PG11