Re: pg_upgrade --copy-file-range - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: pg_upgrade --copy-file-range
Date
Msg-id 73fcc32a-9ea4-4f63-9dda-0102bb143c53@eisentraut.org
Whole thread Raw
In response to Re: pg_upgrade --copy-file-range  (Thomas Munro <thomas.munro@gmail.com>)
Responses Re: pg_upgrade --copy-file-range
List pgsql-hackers
On 08.10.23 07:15, Thomas Munro wrote:
>> About your patch:
>>
>> I think you should have a "check" function called from
>> check_new_cluster().  That check function can then also handle the "not
>> supported" case, and you don't need to handle that in
>> parseCommandLine().  I suggest following the clone example for these,
>> since the issues there are very similar.
> 
> Done.

This version looks good to me.

Tiny nit:  You copy-and-pasted "%s/PG_VERSION.clonetest"; maybe choose a 
different suffix.



pgsql-hackers by date:

Previous
From: shveta malik
Date:
Subject: Re: Synchronizing slots from primary to standby
Next
From: Peter Eisentraut
Date:
Subject: Re: ALTER COLUMN ... SET EXPRESSION to alter stored generated column's expression