Re: binary version of pg_current_wal_insert_lsn and pg_walfile_name functions

From: Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>
To: Ashutosh Sharma <ashu(dot)coek88(at)gmail(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: binary version of pg_current_wal_insert_lsn and pg_walfile_name functions
Date: 2022-09-22 02:10:56
Message-ID: CALj2ACUfbVeSAp2BrzMQWqnGGhHuW=vJBwkR+TP6SiEcboeGFQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Sep 21, 2022 at 9:53 PM Ashutosh Sharma <ashu(dot)coek88(at)gmail(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message osumi.takamichi@fujitsu.com 2022-09-22 03:22:04 RE: Allow logical replication to copy tables in binary format
Previous Message Amit Kapila 2022-09-22 02:00:54 Re: why can't a table be part of the same publication as its schema