diff options
| author | Michael Paquier <michael@paquier.xyz> | 2025-04-23 15:33:07 +0900 |
|---|---|---|
| committer | Michael Paquier <michael@paquier.xyz> | 2025-04-23 15:33:07 +0900 |
| commit | 0ff95e0a5be1372bfba9db284ea17c8e0e5da3a0 (patch) | |
| tree | 5642f266b568796c25e64ad11ffce18b8214c283 /src/test/modules/test_json_parser/test_json_parser_incremental.c | |
| parent | 0e091ce409e06cd89baf81306cc92c496d8ba58d (diff) | |
| download | postgresql-0ff95e0a5be1372bfba9db284ea17c8e0e5da3a0.tar.gz postgresql-0ff95e0a5be1372bfba9db284ea17c8e0e5da3a0.zip | |
psql: Rework TAP routine psql_fails_like() to define WAL sender context
The routine was coded so as a WAL sender was always used, state required
only for one failure test related to START_REPLICATION. This test is
changed so as a WAL sender is used by passing a replication option to
psql_fails_like(), instead of forcing the use of a WAL sender for all
the tests.
This has come up as useful in the context of a separate bug fix where
we are looking at extending tests for some failure scenarios. These
tests need to happen in the context of a normal backend, and not a WAL
sender where the extended query protocol cannot be used.
Discussion: https://postgr.es/m/aAXkJIOildLUA7vQ@paquier.xyz
Diffstat (limited to 'src/test/modules/test_json_parser/test_json_parser_incremental.c')
0 files changed, 0 insertions, 0 deletions