Reimplement nullification of walsender timestamp
authorAlvaro Herrera <alvherre@alvh.no-ip.org>
Wed, 8 Jan 2020 17:33:49 +0000 (14:33 -0300)
committerAlvaro Herrera <alvherre@alvh.no-ip.org>
Wed, 8 Jan 2020 17:33:49 +0000 (14:33 -0300)
commitf5d28710c707ad602cd869602e092cc9d538cbb9
tree816bbbcb06ed70357a2fa377e09a23f325dadfd8
parent913bbd88dc6b859c70ebb48107b38d693c4c6673
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
src/backend/access/transam/xact.c
src/backend/utils/adt/pgstatfuncs.c