Re: Better HINT message for "unexpected data beyond EOF"

On Thu, Mar 27, 2025 at 10:12 AM Andres Freund <andres(at)anarazel(dot)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