Re: pgsql: Refactor all TAP test suites doing connection checks

Michael Paquier <michael@paquier.xyz> writes:
> Refactor all TAP test suites doing connection checks

Some of the buildfarm seems not to like this.  gaur failed here:

==~_~===-=-===~_~== pgsql.build/src/test/authentication/tmp_check/log/regress_log_001_password ==~_~===-=-===~_~==
...
ok 8 - authentication success for method md5, role md5_role
### Reloading node "primary"
# Running: pg_ctl -D
/home/bfarm/bf-data/HEAD/pgsql.build/src/test/authentication/tmp_check/t_001_password_primary_data/pgdatareload 
server signaled
ack Broken pipe: write( 11, 'SELECT $$connected with user=scram_role$$' ) at
/opt/perl5.8.9/lib/site_perl/5.8.9/IPC/Run/IO.pmline 558 

and I think hoverfly's failure is the same thing.

I didn't look at the code, but I bet this is similar to the race
conditions we've seen before where a server process may exit before
the perl test script finishes stuffing a command down the pipe.

            regards, tom lane