Re: Rethink the wait event names for postgres_fdw, dblink and etc

Masahiro Ikeda <ikedamsh@oss.nttdata.com>

View thread View on postgr.es

From: Masahiro Ikeda <ikedamsh@oss.nttdata.com>

To: Michael Paquier <michael@paquier.xyz>

Cc: pgsql-hackers <pgsql-hackers@postgresql.org>

Date: 2023-08-21T02:04:23Z

Lists: pgsql-hackers

Attachments

v2-0001-Make-to-use-custom-wait-events-for-modules.patch (text/x-diff) patch v2-0001

Hi,

Thanks for your comments.

I updated the patch to v2.
* Update a comment instead writing documentation about
   the wait events for pg_prewarm.
* Make the name of wait events which are different code
   path different. Add DblinkGetConnect and PgPrewarmDumpShutdown.
* Make variable names shorter like pgfdw_we_receive.
* Update documents.
* Add some tests with pg_wait_events view.

Regards,
-- 
Masahiro Ikeda
NTT DATA CORPORATION

Commits

dblink: Replace WAIT_EVENT_EXTENSION with custom wait events
- c789f0f6cc5d 17.0 landed
postgres_fdw: Replace WAIT_EVENT_EXTENSION with custom wait events
- d61f2538a39f 17.0 landed
test_shm_mq: Replace WAIT_EVENT_EXTENSION with custom wait events
- 3338a9838298 17.0 landed
worker_spi: Rename custom wait event to "WorkerSpiMain"
- c8e318b1b8d9 17.0 landed