Re: moving basebackup code to its own directory

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Magnus Hagander <magnus(at)hagander(dot)net>
Cc: David Steele <david(at)pgmasters(dot)net>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: moving basebackup code to its own directory
Date: 2022-08-09 17:32:49
Message-ID: CA+TgmoZ24AiN+u5cjrqeiqks7gOGNcNrpdyUaAhHqCXFimE1yA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Aug 9, 2022 at 12:43 PM Magnus Hagander <magnus(at)hagander(dot)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.

--
Robert Haas
EDB: http://www.enterprisedb.com

Attachment Content-Type Size
v1-0001-Move-basebackup-code-to-new-directory-src-backend.patch application/octet-stream 17.7 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2022-08-09 17:43:43 Re: dropping datumSort field
Previous Message Andres Freund 2022-08-09 16:53:19 Re: shared-memory based stats collector - v70