aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/gist/gistproc.c
diff options
context:
space:
mode:
authorMagnus Hagander <magnus@hagander.net>2017-12-29 16:19:51 +0100
committerMagnus Hagander <magnus@hagander.net>2017-12-29 16:28:32 +0100
commitd02974e32e028fc078d8f5eca1d6a4516efb0aa6 (patch)
tree1b2a2114bba40a290a11251bb3838665e2825e4c /src/backend/access/gist/gistproc.c
parent48c9f4926562278a2fd2b85e7486c6d11705f177 (diff)
downloadpostgresql-d02974e32e028fc078d8f5eca1d6a4516efb0aa6.tar.gz
postgresql-d02974e32e028fc078d8f5eca1d6a4516efb0aa6.zip
Properly set base backup backends to active in pg_stat_activity
When walsenders were included in pg_stat_activity, only the ones actually streaming WAL were listed as active when they were active. In particular, the connections sending base backups were listed as being idle. Which means that a regular pg_basebackup would show up with one active and one idle connection, when both were active. This patch updates to set all walsenders to active when they are (including those doing very fast things like IDENTIFY_SYSTEM), and then back to idle. Details about exactly what they are doing is available in pg_stat_replication. Patch by me, review by Michael Paquier and David Steele.
Diffstat (limited to 'src/backend/access/gist/gistproc.c')
0 files changed, 0 insertions, 0 deletions