| From: | Alexander Kukushkin <cyberdemn(at)gmail(dot)com> |
|---|---|
| To: | Andrey Borodin <x4mmm(at)yandex-team(dot)ru> |
| Cc: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Allow reading LSN written by walreciever, but not flushed yet |
| Date: | 2025-05-14 07:02:47 |
| Message-ID: | CAFh8B=nHMz6hWPhdptw9uPHwKR0FMCdf46YG3MkwF0DRUqFNFA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, 12 May 2025 at 17:48, Andrey Borodin <x4mmm(at)yandex-team(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Richard Guo | 2025-05-14 07:06:12 | Re: Assert failure in base_yyparse |
| Previous Message | Alexander Kukushkin | 2025-05-14 06:54:05 | Re: Allow reading LSN written by walreciever, but not flushed yet |