At Mon, 07 Feb 2022 13:21:53 +0900 (JST), Kyotaro Horiguchi
wrote in
> At Fri, 4 Feb 2022 14:50:57 -0800, Nathan Bossart
> wrote in
> > On Fri, Feb 04, 2022 at 09:17:54AM -0500, Robert Haas wrote:
> > > On Fri, Feb 4, 2022 at 9:05 AM Ashutosh Bapat
> > > wrote:
> > >> And it gives some surpr
At Fri, 4 Feb 2022 14:50:57 -0800, Nathan Bossart
wrote in
> On Fri, Feb 04, 2022 at 09:17:54AM -0500, Robert Haas wrote:
> > On Fri, Feb 4, 2022 at 9:05 AM Ashutosh Bapat
> > wrote:
> >> And it gives some surprising results as well
> >> ---
> >> #select pg_walfile_name('0/0'::pg_lsn);
> >>
On Fri, Feb 04, 2022 at 09:17:54AM -0500, Robert Haas wrote:
> On Fri, Feb 4, 2022 at 9:05 AM Ashutosh Bapat
> wrote:
>> And it gives some surprising results as well
>> ---
>> #select pg_walfile_name('0/0'::pg_lsn);
>> pg_walfile_name
>> --
>> 000100FF
On Fri, Feb 4, 2022 at 9:05 AM Ashutosh Bapat
wrote:
> And it gives some surprising results as well
> ---
> #select pg_walfile_name('0/0'::pg_lsn);
> pg_walfile_name
> --
> 000100FF
> (1 row)
>
Yeah, that seems wrong.
--
Robert Haas
EDB: http:/
Hi All,
pg_walfile_name() returns the WAL file name corresponding to the given
WAL location. Per
https://www.postgresql.org/docs/14/functions-admin.html
---
pg_walfile_name ( lsn pg_lsn ) → text
Converts a write-ahead log location to the name of the WAL file
holding that location.
---
The functio
