Re: pg_upgrade --copy-file-range

From: Peter Eisentraut <peter(at)eisentraut(dot)org>
To: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_upgrade --copy-file-range
Date: 2023-11-13 07:15:01
Message-ID: 73fcc32a-9ea4-4f63-9dda-0102bb143c53@eisentraut.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2023-11-13 08:10:29 Re: ALTER COLUMN ... SET EXPRESSION to alter stored generated column's expression
Previous Message shveta malik 2023-11-13 06:38:37 Re: Synchronizing slots from primary to standby