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

From Alvaro Herrera
Subject Re: moving basebackup code to its own directory
Date
Msg-id 20220810165734.bah55lodfmqgfbqa@alvherre.pgsql
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
List pgsql-hackers
On 2022-Aug-10, Robert Haas wrote:

> 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?

Given that 10 of these 11 files are new in 15, I definitely agree with
backpatching the move.

Moving the include/ files is going to cause some pain for any
third-party code #including those files.  I don't think this is a
problem.

-- 
Álvaro Herrera        Breisgau, Deutschland  —  https://www.EnterpriseDB.com/



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: designated initializers
Next
From: Bruce Momjian
Date:
Subject: Re: [PATCH] CF app: add "Returned: Needs more interest"