Re: binary version of pg_current_wal_insert_lsn and pg_walfile_name functions - Mailing list pgsql-hackers

From Bharath Rupireddy
Subject Re: binary version of pg_current_wal_insert_lsn and pg_walfile_name functions
Date
Msg-id CALj2ACUfbVeSAp2BrzMQWqnGGhHuW=vJBwkR+TP6SiEcboeGFQ@mail.gmail.com
Whole thread Raw
In response to Re: binary version of pg_current_wal_insert_lsn and pg_walfile_name functions  (Ashutosh Sharma <ashu.coek88@gmail.com>)
Responses Re: binary version of pg_current_wal_insert_lsn and pg_walfile_name functions
List pgsql-hackers
On Wed, Sep 21, 2022 at 9:53 PM Ashutosh Sharma <ashu.coek88@gmail.com> wrote:
>
> Yeah, we can either add this functionality to pg_waldump or maybe add
> a new binary itself that would return this information.

IMV, a separate tool isn't the way, since pg_waldump already reads WAL
files and decodes WAL records, what's proposed here can be an
additional functionality of pg_waldump.

It will be great if an initial patch is posted here.

-- 
Bharath Rupireddy
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com



pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Re: why can't a table be part of the same publication as its schema
Next
From: "osumi.takamichi@fujitsu.com"
Date:
Subject: RE: Allow logical replication to copy tables in binary format