Re: pg_upgrade: Make testing different transfer modes easier
Peter Eisentraut <peter.eisentraut@enterprisedb.com>
From: Peter Eisentraut <peter.eisentraut@enterprisedb.com>
To: Kyotaro Horiguchi <horikyota.ntt@gmail.com>
Cc: pgsql-hackers@postgresql.org
Date: 2022-12-07T16:30:44Z
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.
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
pg_upgrade: Add --copy option
- 746915c68669 16.0 landed
-
pg_upgrade: Make testing different transfer modes easier
- b059a2409faf 16.0 landed