Re: START_REPLICATION silently truncates an overlong LSN component

From: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
To: "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(dot)com>
Cc: Jan Nidzwetzki <jan(at)planetscale(dot)com>, Ayush Tiwari <ayushtiwari(dot)slg01(at)gmail(dot)com>, ♂π≌26218 <1991230470(at)qq(dot)com>, pgsql-bugs <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: START_REPLICATION silently truncates an overlong LSN component
Date: 2026-10-28 10:50:35
Message-ID: CAHGQGwFc7g1W+2GZj6z1UT61Yugg7WGxhgNpkbqDcA8d0p3pkg@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Wed, Oct 28, 2026 at 12:18 PM Hayato Kuroda (Fujitsu)
<kuroda(dot)hayato(at)fujitsu(dot)com> wrote:
> Hmm. But 5ffb8c74 also did not have any tests and the error "syntax error in history file:"
> is nor verified, right? I still feel we can follow the manner.

I'm not convinced that 0002 and 0003 are necessary. OTOH, there seems to be
general agreement on 0001, so barring any objections, I'll commit that patch.

Regards,

--
Fujii Masao

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Kirill Reshke 2026-10-28 10:56:31 Re: pg_trgm: GiST index scan misses rows at the default word_similarity_threshold
Previous Message Amit Langote 2026-10-28 10:39:45 Re: BUG #19786: JSON_TABLE: subquery in PASSING gives "unexpected non-SELECT command in SubLink"