Re: Logical Replication of sequences - Mailing list pgsql-hackers

From Peter Smith
Subject Re: Logical Replication of sequences
Date
Msg-id CAHut+PusyM1AVBFFN4owevRbqwzJ5_bDDiWUdugD5UDhvtoQew@mail.gmail.com
Whole thread Raw
In response to Re: Logical Replication of sequences  (Peter Smith <smithpb2250@gmail.com>)
Responses Re: Logical Replication of sequences
List pgsql-hackers
Hi Vignesh,

Some minor review comments for the patch v20241230-0003.

======
src/backend/replication/logical/syncutils.c

1.
+ * syncutils.c
+ *   PostgreSQL logical replication: common synchronization code
+ *
+ * Copyright (c) 2024, PostgreSQL Global Development Group

Happy New Year.

s/2024/2025/

~~~

2.
+/*
+ * Enum representing the overall state of subscription relations state.
+ *
+ * SYNC_RELATIONS_STATE_NEEDS_REBUILD indicates that the subscription relations
+ * state is no longer valid and the subscription relations should be rebuilt.
+ *
+ * SYNC_RELATIONS_STATE_REBUILD_STARTED indicates that the subscription
+ * relations state is being rebuilt.
+ *
+ * SYNC_RELATIONS_STATE_VALID indicates that subscription relation state is
+ * up-to-date and valid.
+ */

2a.
That first sentence saying "overall state of [...] state" is a bit strange.

Maybe it can be reworded something like:
Enum for phases of the subscription relations state.

~

2b.
/is no longer valid and/is no longer valid, and/

`

2c.
/that subscription relation state is up-to-date/that the subscription
relation state is up-to-date/

======
Kind Regards,
Peter Smith.
Fujitsu Australia



pgsql-hackers by date:

Previous
From: Tomas Vondra
Date:
Subject: Re: Add the ability to limit the amount of memory that can be allocated to backends.
Next
From: Amit Kapila
Date:
Subject: Re: Conflict detection for update_deleted in logical replication