pg_upgrade: Make testing different transfer modes easier - Mailing list pgsql-hackers

From Peter Eisentraut
Subject pg_upgrade: Make testing different transfer modes easier
Date
Msg-id 50a97009-8ff9-ca4d-a0f6-6086a6775a5b@enterprisedb.com
Whole thread Raw
Responses Re: pg_upgrade: Make testing different transfer modes easier  (Kyotaro Horiguchi <horikyota.ntt@gmail.com>)
Re: pg_upgrade: Make testing different transfer modes easier  (Daniel Gustafsson <daniel@yesql.se>)
List pgsql-hackers
I wanted to test the different pg_upgrade transfer modes (--link, 
--clone), but that was not that easy, because there is more than one 
place in the test script you have to find and manually change.  So I 
wrote a little patch to make that easier.  It's still manual, but it's a 
start.  (In principle, we could automatically run the tests with each 
supported mode in a loop, but that would be very slow.)

While doing that, I also found it strange that the default transfer mode 
(referred to as "copy" internally) did not have any external 
representation, so it is awkward to refer to it in text, and obscure to 
see where it is used for example in those test scripts.  So I added an 
option --copy, which effectively does nothing, but it's not uncommon to 
have options that select default behaviors explicitly.  (I 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?
Attachment

pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: File API cleanup
Next
From: Bruce Momjian
Date:
Subject: Re: New docs chapter on Transaction Management and related changes