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

From Justin Pryzby
Subject Re: moving basebackup code to its own directory
Date
Msg-id 20220809184016.GE19644@telsasoft.com
Whole thread Raw
In response to Re: moving basebackup code to its own directory  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: moving basebackup code to its own directory
Re: moving basebackup code to its own directory
List pgsql-hackers
On Tue, Aug 09, 2022 at 01:32:49PM -0400, Robert Haas wrote:
> On Tue, Aug 9, 2022 at 12:43 PM Magnus Hagander <magnus@hagander.net> wrote:
> >> > So maybe src/backend/backup? Or is that too grandiose for the amount
> >> > of stuff we have here?
> >>
> >> +1 for src/backend/backup. I'd also be happy to see the start/stop code
> >> move here at some point.
> >
> > Yeah, sounds reasonable. There's never an optimal source code layout, but I agree this one is better than putting
itunder replication.
 
> 
> OK, here's a patch.

It looks like this updates the header comments in the .h files but not the .c
files.

Personally, I find these to be silly boilerplate ..

-- 
Justin



pgsql-hackers by date:

Previous
From: Nathan Bossart
Date:
Subject: Re: Avoid erroring out when unable to remove or parse logical rewrite files to save checkpoint work
Next
From: Andres Freund
Date:
Subject: Re: Reducing the chunk header sizes on all memory context types