Horton

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

Christoph Berg <myon@debian.org>

View thread View on postgr.es
From: Christoph Berg <myon@debian.org>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Andres Freund <andres@anarazel.de>, Jakub Wartak <jakub.wartak@enterprisedb.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2025-03-27T15:00:18Z
Lists: pgsql-hackers 
Re: Robert Haas
> 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.

HINT:  Did anything besides PostgreSQL touch that file?

Christoph

Commits

  1. Remove misleading hint for "unexpected data beyond EOF" error.

  2. md: Add comment & assert to buffer-zeroing path in md[start]readv()