| From: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
|---|---|
| To: | Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: pg_upgrade: Make testing different transfer modes easier |
| Date: | 2022-12-07 16:30:44 |
| Message-ID: | 5ff34416-931a-4de5-f954-8e2fa43623f5@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 02.12.22 01:56, Kyotaro Horiguchi wrote:
>> also thought about something like a "mode" option with an argument,
>> but given that we already have --link and --clone, this seemed the
>> most sensible.)
>>
>> Thoughts?
>
> When I read up to the point of the --copy option, what came to my mind
> was the --mode=<blah> option. IMHO, if I was going to add an option
> to choose the copy behavior, I would add --mode option instead, like
> pg_ctl does, as it implicitly signals that the suboptions are mutually
> exclusive.
Ok, we have sort of one vote for each variant now. Let's see if there
are other opinions.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2022-12-07 16:33:06 | Re: pg_upgrade: Make testing different transfer modes easier |
| Previous Message | David G. Johnston | 2022-12-07 16:26:12 | Re: [DOCS] Stats views and functions not in order? |