From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
---|---|
To: | Amit Kapila <akapila(at)postgresql(dot)org>, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com> |
Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Re: pgsql: Add ALTER SUBSCRIPTION ... SKIP. |
Date: | 2022-09-04 08:18:21 |
Message-ID: | 20220904081821.bck6q2j6gfp3p2im@alvherre.pgsql |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers pgsql-hackers |
On 2022-Mar-22, Amit Kapila wrote:
> Add ALTER SUBSCRIPTION ... SKIP.
There are two messages here that seem oddly worded.
msgid "start skipping logical replication transaction finished at %X/%X"
msgid "done skipping logical replication transaction finished at %X/%X"
Two complaints here. First, the phrases "start / finished" and "done /
finished" look very strange. It took me a while to realize that
"finished" refers to the LSN, not to the skipping operation. Do we ever
talk about a transaction "finished at XYZ" as opposed to a transaction
whose LSN is XYZ? (This became particularly strange when I realized
that the LSN might come from a PREPARE.)
Second, "logical replication transaction". Is it not a regular
transaction that we happen to be processing via logical replication?
I think they should say something like
"logical replication starts skipping transaction with LSN %X/%X"
"logical replication completed skipping transaction with LSN %X/%X"
Other ideas?
--
Álvaro Herrera 48°01'N 7°57'E — https://www.EnterpriseDB.com/
Officer Krupke, what are we to do?
Gee, officer Krupke, Krup you! (West Side Story, "Gee, Officer Krupke")
From | Date | Subject | |
---|---|---|---|
Next Message | John Naylor | 2022-09-04 09:36:20 | Re: pgsql: Build all Flex files standalone |
Previous Message | Alvaro Herrera | 2022-09-04 07:54:50 | Re: pgsql: Prefetch data referenced by the WAL, take II. |
From | Date | Subject | |
---|---|---|---|
Next Message | Dilip Kumar | 2022-09-04 10:20:01 | Re: Add 64-bit XIDs into PostgreSQL 15 |
Previous Message | Ibrar Ahmed | 2022-09-04 07:56:58 | Re: pgbench: using prepared BEGIN statement in a pipeline could cause an error |