diff options
| author | Andres Freund <andres@anarazel.de> | 2025-02-19 09:41:08 -0500 |
|---|---|---|
| committer | Andres Freund <andres@anarazel.de> | 2025-02-19 09:45:09 -0500 |
| commit | c0bc11aebb01bc22fe7321379b9ac5ce24388390 (patch) | |
| tree | 2e921cc73adb30f79e2ea7748ad28d600508927b /src/tutorial/advanced.source | |
| parent | f4b08ccb4ec8877b3bf2f617b56244422921a273 (diff) | |
backport: Extend background_psql() to be able to start asynchronously
This is a backport of ba08edb0654. Originally it was only applied to master,
but I (Andres) am planning to fix a few bugs in BackgroundPsql, which would be
somewhat harder with the behavioural differences across branches. It's also
generally good for test infrastructure to behave similarly across branches, to
avoid pain during backpatching.
Discussion: https://postgr.es/m/ilcctzb5ju2gulvnadjmhgatnkxsdpac652byb2u3d3wqziyvx@fbuqcglker46
Michael's original commit message:
This commit extends the constructor routine of BackgroundPsql.pm with a
new "wait" parameter. If set to 0, the routine returns without waiting
for psql to start, ready to consume input.
background_psql() in Cluster.pm gains the same "wait" parameter. The
default behavior is still to wait for psql to start. It becomes now
possible to not wait, giving to TAP scripts the possibility to perform
actions between a BackgroundPsql startup and its wait_connect() call.
Author: Jacob Champion
Discussion: https://postgr.es/m/CAOYmi+=60deN20WDyCoHCiecgivJxr=98s7s7-C8SkXwrCfHXg@mail.gmail.com
Diffstat (limited to 'src/tutorial/advanced.source')
0 files changed, 0 insertions, 0 deletions