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

From: Masahiro Ikeda <ikedamsh(at)oss(dot)nttdata(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Rethink the wait event names for postgres_fdw, dblink and etc
Date: 2023-08-21 02:04:23
Message-ID: b6c00f40075040dcb71f38360a6f45d0@oss.nttdata.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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

Attachment Content-Type Size
v2-0001-Make-to-use-custom-wait-events-for-modules.patch text/x-diff 17.3 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Kyotaro Horiguchi 2023-08-21 02:33:28 Re: Fix pg_stat_reset_single_table_counters function
Previous Message Andy Fan 2023-08-21 01:31:56 Re: Extract numeric filed in JSONB more effectively