]> granicus.if.org Git - postgresql/commit
Fix inadequacies in recently added wait events
authorAlvaro Herrera <alvherre@alvh.no-ip.org>
Tue, 8 Aug 2017 19:37:44 +0000 (15:37 -0400)
committerAlvaro Herrera <alvherre@alvh.no-ip.org>
Tue, 8 Aug 2017 19:37:44 +0000 (15:37 -0400)
commit030273b7ea468ed4b3073dfd1f2ad88e3129df6a
tree7a1385e2de7253c79a2ee2c454fef34ba7ff8110
parentb4a2eea030ba74ea84335c7d5bc999f693ffd9a4
Fix inadequacies in recently added wait events

In commit 9915de6c1cb2, we introduced a new wait point for replication
slots and incorrectly labelled it as wait event PG_WAIT_LOCK.  That's
wrong, so invent an appropriate new wait event instead, and document it
properly.

While at it, fix numerous other problems in the vicinity:
- two different walreceiver wait events were being mixed up in a single
  wait event (which wasn't documented either); split it out so that they
  can be distinguished, and document the new events properly.

- ParallelBitmapPopulate was documented but didn't exist.

- ParallelBitmapScan was not documented (I think this should be called
  "ParallelBitmapScanInit" instead.)

- Logical replication wait events weren't documented

- various symbols had been added in dartboard order in various places.
  Put them in alphabetical order instead, as was originally intended.

Discussion: https://postgr.es/m/20170808181131.mu4fjepuh5m75cyq@alvherre.pgsql
doc/src/sgml/monitoring.sgml
src/backend/postmaster/pgstat.c
src/backend/replication/libpqwalreceiver/libpqwalreceiver.c
src/backend/replication/slot.c
src/include/pgstat.h