Skip to content

Commit fce9ba8

Browse files
committed
pg_stat_activity: show NULL stmt start time for walsenders
Returning a non-NULL time is pointless, sinc a walsender is not a process that would be running normal transactions anyway, but the code was unintentionally exposing the process start time intermittently, which was not only bogus but it also confused monitoring systems looking for idle transactions. Fix by avoiding all updates in walsenders. Backpatch to 11, where walsenders started appearing in pg_stat_activity. Reported-by: Tomas Vondra Discussion: https://postgr.es/m/20191209234409.exe7osmyalwkt5j4@development
1 parent b898452 commit fce9ba8

File tree

1 file changed

+7
-0
lines changed
  • src/backend/access/transam

1 file changed

+7
-0
lines changed

src/backend/access/transam/xact.c

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -817,6 +817,13 @@ GetCurrentTransactionStopTimestamp(void)
817817
void
818818
SetCurrentStatementStartTimestamp(void)
819819
{
820+
/*
821+
* Skip if on a walsender; this is not needed, and it confuses monitoring
822+
* if we publish non-NULL values.
823+
*/
824+
if (am_walsender)
825+
return;
826+
820827
if (!IsParallelWorker())
821828
stmtStartTimestamp = GetCurrentTimestamp();
822829
else

0 commit comments

Comments
 (0)