Re: moving basebackup code to its own directory - Mailing list pgsql-hackers

From Magnus Hagander
Subject Re: moving basebackup code to its own directory
Date
Msg-id CABUevEwYdLsJMaJ1jqHwYOrbiEBYV=q5yMKfAqOumWFU-7TtVA@mail.gmail.com
Whole thread Raw
In response to Re: moving basebackup code to its own directory  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: moving basebackup code to its own directory
List pgsql-hackers
On Wed, Aug 10, 2022 at 6:20 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
>
> Robert Haas <robertmhaas@gmail.com> writes:
> > David Steele voted for back-patching this on the grounds that it would
> > make future back-patching easier, which is an argument that seems to
> > me to have some merit, although on the other hand, we are already into
> > August so it's quite late in the day. Anyone else want to vote?
>
> Seems like low-risk refactoring, so +1 for keeping v15 close to HEAD.

+1, but I suggest also getting a hat-tip from the RMT on it.

-- 
 Magnus Hagander
 Me: https://www.hagander.net/
 Work: https://www.redpill-linpro.com/



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: moving basebackup code to its own directory
Next
From: "Jonathan S. Katz"
Date:
Subject: Re: moving basebackup code to its own directory