| From: | Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com> |
|---|---|
| To: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Make pg_waldump report replication origin ID, LSN, and timestamp. |
| Date: | 2021-12-06 07:35:07 |
| Message-ID: | CAD21AoD2dJfgsdxk4_KciAZMZQoUiCvmV9sDpp8ZuKLtKCNXaA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi all,
I realized that pg_waldump doesn't show replication origin ID, LSN,
and timestamp of PREPARE TRANSACTION record. Commit 7b8a899bdeb
improved pg_waldump two years ago so that it reports the detail of
information of PREPARE TRANSACTION but ISTM that it overlooked showing
replication origin information. As far as I can see in the discussion
thread[1], there was no discussion on that. These are helpful when
diagnosing 2PC related issues on the subscriber side.
I've attached a patch to add replication origin information to
xact_desc_prepare().
Regards,
--
Masahiko Sawada
EDB: https://www.enterprisedb.com/
| Attachment | Content-Type | Size |
|---|---|---|
| 0001-Make-pg_waldump-report-replication-origin-ID-LSN-and.patch | application/x-patch | 2.2 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2021-12-06 08:09:27 | Re: Make pg_waldump report replication origin ID, LSN, and timestamp. |
| Previous Message | Amit Langote | 2021-12-06 07:30:00 | Re: pg_get_publication_tables() output duplicate relid |