pgsql: Reimplement nullification of walsender timestamp

From: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Reimplement nullification of walsender timestamp
Date: 2020-01-08 17:34:18
Message-ID: E1ipFDm-0002GA-PB@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Reimplement nullification of walsender timestamp

Make the value null only at pg_stat_activity-output time, as suggested
by Tom Lane, instead of messing with the internal state. This should
appease buildfarm members with force_parallel_mode=regress, which are
running parallel queries on logical replication walsenders.

The fact that walsenders can run parallel queries should perhaps be
studied more carefully, but for the moment let's get rid of the red
blots in buildfarm.

Backpatch to pg10, like the previous commit.

Discussion: https://postgr.es/m/30804.1578438763@sss.pgh.pa.us

Branch
------
REL_10_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/da42b9f3ff4375972e535368e875ca0dbbdf322a

Modified Files
--------------
src/backend/access/transam/xact.c | 7 -------
src/backend/utils/adt/pgstatfuncs.c | 8 +++++++-
2 files changed, 7 insertions(+), 8 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Peter Eisentraut 2020-01-08 21:59:13 pgsql: Modernize Python exception syntax in tests
Previous Message Tom Lane 2020-01-08 16:08:27 pgsql: Improve the handling of result type coercions in SQL functions.