Re: moving basebackup code to its own directory
Justin Pryzby <pryzby@telsasoft.com>
From: Justin Pryzby <pryzby@telsasoft.com>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Magnus Hagander <magnus@hagander.net>, David Steele <david@pgmasters.net>, pgsql-hackers@postgresql.org
Date: 2022-08-09T18:40:16Z
Lists: 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 it under 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
Commits
-
Move basebackup code to new directory src/backend/backup
- a8c012869763 16.0 landed
- f88798c098d2 15.0 landed