Re: Allow reading LSN written by walreciever, but not flushed yet - Mailing list pgsql-hackers

From Alexander Kukushkin
Subject Re: Allow reading LSN written by walreciever, but not flushed yet
Date
Msg-id CAFh8B=nHMz6hWPhdptw9uPHwKR0FMCdf46YG3MkwF0DRUqFNFA@mail.gmail.com
Whole thread Raw
In response to Small fixes needed by high-availability tools  (Andrey Borodin <x4mmm@yandex-team.ru>)
List pgsql-hackers


On Mon, 12 May 2025 at 17:48, Andrey Borodin <x4mmm@yandex-team.ru> wrote:
Done so. Thanks!

TBH, the current function name pg_last_wal_receive_lsn() is confusing, and introducing a new one pg_last_wal_receive_unflushed_lsn() doesn't make it better :(
What about actually adding TWO new functions, pg_last_wal_write_lsn() and pg_last_wal_flush_lsn()?
These names are more aligned with column names in pg_stat_replication view and speak for themselves.

And, we can keep pg_last_wal_receive_lsn() as an alias of pg_last_wal_flush_lsn() for backward compatibility.

--
Regards,
--
Alexander Kukushkin

pgsql-hackers by date:

Previous
From: Alexander Kukushkin
Date:
Subject: Re: Allow reading LSN written by walreciever, but not flushed yet
Next
From: Richard Guo
Date:
Subject: Re: Assert failure in base_yyparse