Fix badly generated entries in wait_event_names.txt
Hi hackers,
fa88928470 introduced src/backend/utils/activity/wait_event_names.txt that has
been auto-generated. The auto-generation had parsing errors leading to bad
entries in wait_event_names.txt (when the same "WAIT_EVENT" name can be found as
a substring of another one, then descriptions were merged in one of them).
Fixing those bad entries in the attached.
Regards,
--
Bertrand Drouvot
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com
Attachments:
v1-0001-Fix-badly-generated-entries-in-wait_event_names.t.patchtext/plain; charset=UTF-8; name=v1-0001-Fix-badly-generated-entries-in-wait_event_names.t.patchDownload
From fe669c646ea93b66b36d0aa97bb5665f0dd734b7 Mon Sep 17 00:00:00 2001
From: bdrouvotAWS <bdrouvot@amazon.com>
Date: Mon, 7 Aug 2023 07:12:11 +0000
Subject: [PATCH v1] Fix badly generated entries in wait_event_names.txt
fa88928470 introduced src/backend/utils/activity/wait_event_names.txt that has
been auto-generated. The auto-generation had parsing errors leading to bad
entries in wait_event_names.txt (when the same "WAIT_EVENT" name can be found as
a substring of another one, then descriptions were merged in one of them.)
Fixing those bad entries.
---
src/backend/utils/activity/wait_event_names.txt | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
100.0% src/backend/utils/activity/
diff --git a/src/backend/utils/activity/wait_event_names.txt b/src/backend/utils/activity/wait_event_names.txt
index 2ea4789b00..fcd9d2c63c 100644
--- a/src/backend/utils/activity/wait_event_names.txt
+++ b/src/backend/utils/activity/wait_event_names.txt
@@ -137,7 +137,7 @@ WAIT_EVENT_REPLICATION_ORIGIN_DROP ReplicationOriginDrop "Waiting for a replicat
WAIT_EVENT_REPLICATION_SLOT_DROP ReplicationSlotDrop "Waiting for a replication slot to become inactive so it can be dropped."
WAIT_EVENT_RESTORE_COMMAND RestoreCommand "Waiting for <xref linkend="guc-restore-command"/> to complete."
WAIT_EVENT_SAFE_SNAPSHOT SafeSnapshot "Waiting to obtain a valid snapshot for a <literal>READ ONLY DEFERRABLE</literal> transaction."
-WAIT_EVENT_SYNC_REP SyncRep "Waiting for confirmation from a remote server during synchronous replication. Waiting to read or update information about the state of synchronous replication."
+WAIT_EVENT_SYNC_REP SyncRep "Waiting for confirmation from a remote server during synchronous replication."
WAIT_EVENT_WAL_RECEIVER_EXIT WalReceiverExit "Waiting for the WAL receiver to exit."
WAIT_EVENT_WAL_RECEIVER_WAIT_START WalReceiverWaitStart "Waiting for startup process to send initial data for streaming replication."
WAIT_EVENT_XACT_GROUP_UPDATE XactGroupUpdate "Waiting for the group leader to update transaction status at end of a parallel operation."
@@ -177,9 +177,9 @@ WAIT_EVENT_BUFFILE_READ BufFileRead "Waiting for a read from a buffered file."
WAIT_EVENT_BUFFILE_WRITE BufFileWrite "Waiting for a write to a buffered file."
WAIT_EVENT_BUFFILE_TRUNCATE BufFileTruncate "Waiting for a buffered file to be truncated."
WAIT_EVENT_CONTROL_FILE_READ ControlFileRead "Waiting for a read from the <filename>pg_control</filename> file."
-WAIT_EVENT_CONTROL_FILE_SYNC ControlFileSync "Waiting for the <filename>pg_control</filename> file to reach durable storage. Waiting for an update to the <filename>pg_control</filename> file to reach durable storage."
+WAIT_EVENT_CONTROL_FILE_SYNC ControlFileSync "Waiting for the <filename>pg_control</filename> file to reach durable storage."
WAIT_EVENT_CONTROL_FILE_SYNC_UPDATE ControlFileSyncUpdate "Waiting for an update to the <filename>pg_control</filename> file to reach durable storage."
-WAIT_EVENT_CONTROL_FILE_WRITE ControlFileWrite "Waiting for a write to the <filename>pg_control</filename> file. Waiting for a write to update the <filename>pg_control</filename> file."
+WAIT_EVENT_CONTROL_FILE_WRITE ControlFileWrite "Waiting for a write to the <filename>pg_control</filename> file."
WAIT_EVENT_CONTROL_FILE_WRITE_UPDATE ControlFileWriteUpdate "Waiting for a write to update the <filename>pg_control</filename> file."
WAIT_EVENT_COPY_FILE_READ CopyFileRead "Waiting for a read during a file copy operation."
WAIT_EVENT_COPY_FILE_WRITE CopyFileWrite "Waiting for a write during a file copy operation."
@@ -241,9 +241,9 @@ WAIT_EVENT_WAL_COPY_WRITE WALCopyWrite "Waiting for a write when creating a new
WAIT_EVENT_WAL_INIT_SYNC WALInitSync "Waiting for a newly initialized WAL file to reach durable storage."
WAIT_EVENT_WAL_INIT_WRITE WALInitWrite "Waiting for a write while initializing a new WAL file."
WAIT_EVENT_WAL_READ WALRead "Waiting for a read from a WAL file."
-WAIT_EVENT_WAL_SYNC WALSync "Waiting for a WAL file to reach durable storage. Waiting for data to reach durable storage while assigning a new WAL sync method."
+WAIT_EVENT_WAL_SYNC WALSync "Waiting for a WAL file to reach durable storage."
WAIT_EVENT_WAL_SYNC_METHOD_ASSIGN WALSyncMethodAssign "Waiting for data to reach durable storage while assigning a new WAL sync method."
-WAIT_EVENT_WAL_WRITE WALWrite "Waiting for a write to a WAL file. Waiting for WAL buffers to be written to disk."
+WAIT_EVENT_WAL_WRITE WALWrite "Waiting for a write to a WAL file."
#
--
2.34.1
On Mon, Aug 07, 2023 at 10:34:43AM +0200, Drouvot, Bertrand wrote:
fa88928470 introduced src/backend/utils/activity/wait_event_names.txt that has
been auto-generated. The auto-generation had parsing errors leading to bad
entries in wait_event_names.txt (when the same "WAIT_EVENT" name can be found as
a substring of another one, then descriptions were merged in one of them).
Thanks for the patch, applied. I have double-checked the contents of
the tables and the five entries you have pointed out are the only ones
with duplicated descriptions.
--
Michael
Hi,
On 8/8/23 1:25 AM, Michael Paquier wrote:
On Mon, Aug 07, 2023 at 10:34:43AM +0200, Drouvot, Bertrand wrote:
fa88928470 introduced src/backend/utils/activity/wait_event_names.txt that has
been auto-generated. The auto-generation had parsing errors leading to bad
entries in wait_event_names.txt (when the same "WAIT_EVENT" name can be found as
a substring of another one, then descriptions were merged in one of them).Thanks for the patch, applied.
Thanks!
I have double-checked the contents of
the tables and the five entries you have pointed out are the only ones
with duplicated descriptions.
Yeah, did the same on my side before submitting the patch, and all looks
good now.
Regards,
--
Bertrand Drouvot
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com