Re: Better HINT message for "unexpected data beyond EOF" - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Better HINT message for "unexpected data beyond EOF"
Date
Msg-id CA+TgmoaQNaiSVcDjJBifpcHXkYg+nTHBPq3CJEo10QCRxznZDg@mail.gmail.com
Whole thread Raw
In response to Re: Better HINT message for "unexpected data beyond EOF"  (Andres Freund <andres@anarazel.de>)
Responses Re: Better HINT message for "unexpected data beyond EOF"
List pgsql-hackers
On Thu, Mar 27, 2025 at 10:12 AM Andres Freund <andres@anarazel.de> wrote:
> FWIW, I think we should just drop the HINT. We really have no clue what caused
> it and a HINT should imo have at least some value other than "*Shrug*", which
> is imo pretty much what these HINTs amount to, if they were a bit more blunt.

I think that would be better than what we have now, but I still wonder
if we should give some kind of a hint that an external process may be
doing something to that file. Jakub and I may be biased by having just
seen a case of exactly that in the field, but I wonder now how many
'data beyond EOF' messages are exactly that -- and it's not like the
user is going to guess that 'data beyond EOF' might mean that such a
thing occurred.

--
Robert Haas
EDB: http://www.enterprisedb.com



pgsql-hackers by date:

Previous
From: Vik Fearing
Date:
Subject: Re: SQL:2023 JSON simplified accessor support
Next
From: Christoph Berg
Date:
Subject: Re: Better HINT message for "unexpected data beyond EOF"