On Tue, Sep 20, 2022 at 5:13 PM Bharath Rupireddy <bharath.rupireddyforpostg...@gmail.com> wrote: > > On Mon, Sep 19, 2022 at 8:19 PM Ashutosh Sharma <ashu.coe...@gmail.com> wrote: > > > > Hi All, > > > > Currently, we have pg_current_wal_insert_lsn and pg_walfile_name sql > > functions which gives us information about the next wal insert > > location and the WAL file that the next wal insert location belongs > > to. Can we have a binary version of these sql functions? > > +1 for the idea in general. > > As said, pg_waldump seems to be the right candidate. I think we want > the lsn of the last WAL record and its info and the WAL file name > given an input data directory or just the pg_wal directory or any > directory where WAL files are located. For instance, one can use this > on an archive location containing archived WAL files or on a node > where pg_receivewal is receiving WAL files. Am I missing any other > use-cases? >
Yeah, we can either add this functionality to pg_waldump or maybe add a new binary itself that would return this information. -- With Regards, Ashutosh Sharma.
