NotificationsYou must be signed in to change notification settings
Fork28
Star151

Commitb175bd5

committed

pg_stat_activity: show NULL stmt start time for walsenders

Returning a non-NULL time is pointless, sinc a walsender is not aprocess that would be running normal transactions anyway, but the codewas unintentionally exposing the process start time intermittently,which was not only bogus but it also confused monitoring systems lookingfor idle transactions. Fix by avoiding all updates in walsenders.Backpatch to 11, where walsenders started appearing in pg_stat_activity.Reported-by: Tomas VondraDiscussion:https://postgr.es/m/20191209234409.exe7osmyalwkt5j4@development

1 parentce242ae commitb175bd5Copy full SHA for b175bd5

File tree

1 file changed

-0

lines changed

src/backend/access/transam
- xact.c

1 file changed

-0

lines changed

`‎src/backend/access/transam/xact.c‎`

Lines changed: 7 additions & 0 deletions

Original file line number	Diff line number	Diff line change
`@@ -816,6 +816,13 @@ GetCurrentTransactionStopTimestamp(void)`
`816`	`816`	`void`
`817`	`817`	`SetCurrentStatementStartTimestamp(void)`
`818`	`818`	`{`
	`819`	`+/*`
	`820`	`+ * Skip if on a walsender; this is not needed, and it confuses monitoring`
	`821`	`+ * if we publish non-NULL values.`
	`822`	`+ */`
	`823`	`+if (am_walsender)`
	`824`	`+return;`
	`825`	`+`
`819`	`826`	`if (!IsParallelWorker())`
`820`	`827`	`stmtStartTimestamp=GetCurrentTimestamp();`
`821`	`828`	`else`

0 commit comments

Comments

(0)

Movatterモバイル変換

Navigation Menu

Search code, repositories, users, issues, pull requests...

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Commitb175bd5

File tree

1 file changed

1 file changed

`‎src/backend/access/transam/xact.c‎`

0 commit comments