| From: | vignesh C <vignesh21(at)gmail(dot)com> |
|---|---|
| To: | Ajin Cherian <itsajin(at)gmail(dot)com> |
| Cc: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: repeated decoding of prepared transactions |
| Date: | 2021-02-25 11:34:01 |
| Message-ID: | CALDaNm3CcxG-o1ZFip5AexCSBNnZ2e=FJCKzKy=YtimxH9ZEPw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Feb 24, 2021 at 5:06 PM Ajin Cherian <itsajin(at)gmail(dot)com> wrote:
>
> On Wed, Feb 24, 2021 at 4:48 PM Ajin Cherian <itsajin(at)gmail(dot)com> wrote:
>
> > I plan to split this into two patches next. But do review and let me
> > know if you have any comments.
>
> Attaching an updated patch-set with the changes for
> snapshot_was_exported_at_lsn separated out from the changes for the
> APIs pg_create_logical_replication_slot() and
> pg_logical_slot_get_changes(). Along with a rebase that takes in a few
> more commits since my last patch.
One observation while verifying the patch I noticed that most of
ReplicationSlotPersistentData structure members are displayed in
pg_replication_slots, but I did not see snapshot_was_exported_at_lsn
being displayed. Is this intentional? If not intentional we can
include snapshot_was_exported_at_lsn in pg_replication_slots.
Regards,
Vignesh
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2021-02-25 11:36:00 | Re: repeated decoding of prepared transactions |
| Previous Message | Benoit Lobréau | 2021-02-25 11:24:57 | Re: archive_command / pg_stat_archiver & documentation |