Re: BUG #19598: pg_waldump: -s/-e accept out-of-range WAL locations and silently use the low 32 bits

From: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
To: Zexin Li <lizi(dot)openmind(at)gmail(dot)com>
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org, malis(at)pgrust(dot)com
Subject: Re: BUG #19598: pg_waldump: -s/-e accept out-of-range WAL locations and silently use the low 32 bits
Date: 2026-08-12 08:09:13
Message-ID: CAHGQGwFyLsGnJS5zn8KSmQP5j=rjQcVxroHF8tMB9E5tR8U+5A@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Tue, Aug 11, 2026 at 9:41 AM Zexin Li <lizi(dot)openmind(at)gmail(dot)com> wrote:
>
> On Sun, Aug 10, 2026, Fujii Masao wrote:
> > The main change from v2 is that pg_lsn_in_safe() now also uses
> > pg_parse_lsn(), leaving only the backend-specific soft-error handling
> > there. This avoids duplicating the LSN syntax checks.
>
> Thank you for the review. v3 looks good to me.

I've pushed the patch. Thanks!

Regards,

--
Fujii Masao

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Christoph Berg 2026-08-12 08:37:18 Re: COPY TO regression with psql -c
Previous Message PG Bug reporting form 2026-08-11 22:58:04 BUG #19616: pgoutput sends stream abort ('A') to clients that did not enable streaming