From: | Stephen Frost <sfrost(at)snowman(dot)net> |
---|---|
To: | pgsql-committers(at)postgresql(dot)org |
Subject: | pgsql: test_pg_dump: perltidy cleanup |
Date: | 2017-01-31 16:18:28 |
Message-ID: | E1cYb8W-0006gC-Gi@gemulon.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
test_pg_dump: perltidy cleanup
As pointed out by Alvaro, we actually use perltidy on the perl scripts
in the source tree, so go back to the results of a perltidy run for the
test_pg_dump TAP script.
To make it look slightly less tragic, I changed most of the independent
arguments into long-form single arguments (eg: -f file.sql changed to be
--file=file.sql) to avoid having them confusingly split across lines due
to perltidy.
Back-patch to 9.6, as the last patch was.
Branch
------
REL9_6_STABLE
Details
-------
http://git.postgresql.org/pg/commitdiff/3e9c36165377b07ffb182c366e295ac48ea5d5ba
Modified Files
--------------
src/test/modules/test_pg_dump/t/001_base.pl | 885 ++++++++++++----------------
1 file changed, 377 insertions(+), 508 deletions(-)
From | Date | Subject | |
---|---|---|---|
Next Message | Stephen Frost | 2017-01-31 17:42:30 | pgsql: perltidy pg_dump TAP tests |
Previous Message | Tom Lane | 2017-01-30 23:42:47 | pgsql: Simplify some long-obsolete code in hba.c's next_token(). |