pgsql: Make pg_upgrade's test.sh less chatty.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Make pg_upgrade's test.sh less chatty.
Date: 2019-05-21 17:12:04
Message-ID: E1hT8J2-0007nF-O4@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Make pg_upgrade's test.sh less chatty.

The use of "set -x" to echo a subset of the test's commands might've
been a good idea during development of this test, but it's been stable
for long enough now that the extra output isn't very useful. Also
our project expectations have been trending towards less output in
non-error cases; the fact that "set -x" produces output on stderr
is particularly annoying from that standpoint. So get rid of it.

Also, pass "-A trust" to initdb explicitly so that it won't issue
a warning about "trust" being an insecure default. This matches
what the TAP tests have done for a long time, and again gets rid
of some noise on stderr.

Discussion: https://postgr.es/m/21766.1558397960@sss.pgh.pa.us

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/eb9812f272db8e93416831e5254569b76edf8264

Modified Files
--------------
src/bin/pg_upgrade/test.sh | 10 ++--------
1 file changed, 2 insertions(+), 8 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Andres Freund 2019-05-21 19:52:09 Re: pgsql: Make VACUUM accept 1 and 0 as a boolean value.
Previous Message Tom Lane 2019-05-21 16:51:54 Re: pgsql: Make VACUUM accept 1 and 0 as a boolean value.