Re: Rethink the wait event names for postgres_fdw, dblink and etc
Michael Paquier <michael@paquier.xyz>
From: Michael Paquier <michael@paquier.xyz>
To: Masahiro Ikeda <ikedamsh@oss.nttdata.com>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2023-10-05T01:28:29Z
Lists: pgsql-hackers
On Wed, Oct 04, 2023 at 05:19:40PM +0900, Michael Paquier wrote: > I am lacking a bit of time now, but I have applied the bits for > test_shm_mq and worker_spi. Note that I have not added tests for > test_shm_mq as it may be possible that the two events (for the > bgworker startup and for a message to be queued) are never reached > depending on the timing. I'll handle the rest tomorrow, with likely > some adjustments to the tests. (I may as well just remove them, this > API is already covered by worker_spi.) After sleeping on it, I've taken the decision to remove the tests. As far as I have tested, this was stable, but this does not really improve the test coverage as WaitEventExtensionNew() is covered in worker_spi. I have done tweaks to the docs and the variable names, and applied that into its own commit. Note as well that the docs of dblink were wrong for DblinkGetConnect: the wait event could be seen in other functions than dblink() and dblink_exec(). -- Michael
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