diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2021-10-20 18:44:37 -0400 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2021-10-20 18:44:37 -0400 |
| commit | f45dc59a38cab1d2af6baaedb79559fe2e9b3781 (patch) | |
| tree | 6145d1e1557dda83d944d9706957c8511ce82bb0 /src/test/modules/commit_ts/sql/commit_timestamp.sql | |
| parent | cd124d205c42a623b68cd155ace94cc376851b78 (diff) | |
| download | postgresql-f45dc59a38cab1d2af6baaedb79559fe2e9b3781.tar.gz postgresql-f45dc59a38cab1d2af6baaedb79559fe2e9b3781.zip | |
Improve pg_regress.c's infrastructure for issuing psql commands.
Support issuing more than one "-c command" switch to a single
psql invocation. This allows combining some things that formerly
required two or more backend launches into a single session.
In particular, we can issue DROP DATABASE as one of the -c commands
without getting "DROP DATABASE cannot run inside a transaction block".
In addition to reducing the number of sessions needed, this patch
also suppresses "NOTICE: database "foo" does not exist, skipping"
chatter that was formerly generated during pg_regress's DROP DATABASE
(or ROLE) IF NOT EXISTS calls. That moves us another step closer
to the ideal of not seeing any messages during successful build/test.
This also eliminates some hard-coded restrictions on the length of
the commands issued. I don't think we were anywhere near hitting
those, but getting rid of the limit is comforting.
Patch by me, but thanks to Nathan Bossart for starting the discussion.
Discussion: https://postgr.es/m/DCBAE0E4-BD56-482F-8A70-7FD0DC0860BE@amazon.com
Diffstat (limited to 'src/test/modules/commit_ts/sql/commit_timestamp.sql')
0 files changed, 0 insertions, 0 deletions