Re: moving basebackup code to its own directory

From: David Steele <david(at)pgmasters(dot)net>
To: Robert Haas <robertmhaas(at)gmail(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net>
Cc: "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:49:34
Message-ID: 02ebef75-8d1b-4211-3d8d-7508db4a43d3@pgmasters.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 8/9/22 13:32, Robert Haas wrote:
> 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.

This looks good to me.

Regards,
-David

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jonathan S. Katz 2022-08-09 18:04:48 Re: PG 15 (and to a smaller degree 14) regression due to ExprEvalStep size
Previous Message Robert Haas 2022-08-09 17:43:43 Re: dropping datumSort field