pg.ddx.io pgsql-committers@postgresql.org mailing list archivehelp / color / mirror / Atom feed
pgsql: backport: Extend background_psql() to be able to start asynchron 5+ messages / 1 participants [nested] [flat]
* pgsql: backport: Extend background_psql() to be able to start asynchron @ 2025-02-19 15:40 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 5+ messages in thread From: Andres Freund @ 2025-02-19 15:40 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org 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 Branch ------ REL_17_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/49b6f4a02b2339aac288cf3d363a4e1e9777b5c6 Modified Files -------------- src/test/perl/PostgreSQL/Test/BackgroundPsql.pm | 28 ++++++++++++++++++------- src/test/perl/PostgreSQL/Test/Cluster.pm | 10 ++++++++- 2 files changed, 30 insertions(+), 8 deletions(-) ^ permalink raw reply [nested|flat] 5+ messages in thread
* pgsql: backport: Extend background_psql() to be able to start asynchron @ 2025-02-19 15:40 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 5+ messages in thread From: Andres Freund @ 2025-02-19 15:40 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org 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 Branch ------ REL_16_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/6ab58d506bba28fa46a6c993a7e82d6053651546 Modified Files -------------- src/test/perl/PostgreSQL/Test/BackgroundPsql.pm | 28 ++++++++++++++++++------- src/test/perl/PostgreSQL/Test/Cluster.pm | 10 ++++++++- 2 files changed, 30 insertions(+), 8 deletions(-) ^ permalink raw reply [nested|flat] 5+ messages in thread
* pgsql: backport: Extend background_psql() to be able to start asynchron @ 2025-02-19 15:40 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 5+ messages in thread From: Andres Freund @ 2025-02-19 15:40 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org 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 Branch ------ REL_15_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/c0bc11aebb01bc22fe7321379b9ac5ce24388390 Modified Files -------------- src/test/perl/PostgreSQL/Test/BackgroundPsql.pm | 28 ++++++++++++++++++------- src/test/perl/PostgreSQL/Test/Cluster.pm | 10 ++++++++- 2 files changed, 30 insertions(+), 8 deletions(-) ^ permalink raw reply [nested|flat] 5+ messages in thread
* pgsql: backport: Extend background_psql() to be able to start asynchron @ 2025-02-19 15:40 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 5+ messages in thread From: Andres Freund @ 2025-02-19 15:40 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org 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 Branch ------ REL_14_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/7c07ab62aeb7e8c4c24a5ff85e5c2a3416f257e7 Modified Files -------------- src/test/perl/PostgreSQL/Test/BackgroundPsql.pm | 28 ++++++++++++++++++------- src/test/perl/PostgresNode.pm | 10 ++++++++- 2 files changed, 30 insertions(+), 8 deletions(-) ^ permalink raw reply [nested|flat] 5+ messages in thread
* pgsql: backport: Extend background_psql() to be able to start asynchron @ 2025-02-19 15:40 Andres Freund <andres@anarazel.de> 0 siblings, 0 replies; 5+ messages in thread From: Andres Freund @ 2025-02-19 15:40 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org 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 Branch ------ REL_13_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/6af51bf05a6afd8e10ef53c1c87de3906e2532a9 Modified Files -------------- src/test/perl/PostgreSQL/Test/BackgroundPsql.pm | 28 ++++++++++++++++++------- src/test/perl/PostgresNode.pm | 10 ++++++++- 2 files changed, 30 insertions(+), 8 deletions(-) ^ permalink raw reply [nested|flat] 5+ messages in thread
end of thread, other threads:[~2025-02-19 15:40 UTC | newest] Thread overview: 5+ messages (download: mbox mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 2025-02-19 15:40 pgsql: backport: Extend background_psql() to be able to start asynchron Andres Freund <andres@anarazel.de> 2025-02-19 15:40 pgsql: backport: Extend background_psql() to be able to start asynchron Andres Freund <andres@anarazel.de> 2025-02-19 15:40 pgsql: backport: Extend background_psql() to be able to start asynchron Andres Freund <andres@anarazel.de> 2025-02-19 15:40 pgsql: backport: Extend background_psql() to be able to start asynchron Andres Freund <andres@anarazel.de> 2025-02-19 15:40 pgsql: backport: Extend background_psql() to be able to start asynchron Andres Freund <andres@anarazel.de>
This inbox is served by DDX for PostgreSQL; see mirroring instructions for how to clone and mirror all data and code used for this inbox