MIME-Version: 1.0
From: xiong ding <dingxiong203@gmail.com>
Date: Sun, 1 Sep 2024 18:48:52 -0700
Message-ID: <CAP_sNCaSYLgZVYdT6u7c7CC8aA6CahsLui__ZpZzhsQks0bNew@mail.gmail.com>
Subject: Could we go back in a replication slot?
To: pgsql-general@lists.postgresql.org
Content-Type: multipart/alternative; boundary="0000000000004825e006211925ee"
Archived-At: <https://www.postgresql.org/message-id/CAP_sNCaSYLgZVYdT6u7c7CC8aA6CahsLui__ZpZzhsQks0bNew%40mail.gmail.com>
Precedence: bulk

--0000000000004825e006211925ee
Content-Type: text/plain; charset="UTF-8"

Hi, community,

The START_REPLICATION command accepts a lsn parameter, but according to the
document that replication "starts at either WAL location XXX/XXX or the
slot's confirmed_flush_lsn (see Section 54.19), whichever is greater." I
wonder if there is a way to go back, like a command to set
confirmed_flush_lsn to a previous lsn.

I am asking because I may need to replay the replication messages to Kafka.

Sincerely,
Xiong Ding

--0000000000004825e006211925ee
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi, community,<div><br></div><div>The=C2=A0START_REPLICATI=
ON command accepts a lsn parameter, but according to the document that repl=
ication &quot;starts at either WAL location XXX/XXX or the slot&#39;s confi=
rmed_flush_lsn (see Section 54.19), whichever is greater.&quot; I wonder if=
 there is a way to go back, like a command to set confirmed_flush_lsn to a =
previous lsn.</div><div><br></div><div>I am asking because I may need to re=
play the replication messages to Kafka.</div><div><br></div><div>Sincerely,=
</div><div>Xiong Ding</div><div>=C2=A0</div></div>

--0000000000004825e006211925ee--