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

From: Christoph Berg <myon(at)debian(dot)org>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Jakub Wartak <jakub(dot)wartak(at)enterprisedb(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Better HINT message for "unexpected data beyond EOF"
Date: 2025-04-01 13:54:49
Message-ID: Z-vwKRcOKV93We_k@msg.df7cb.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Re: Robert Haas
> > Another question is should we back-patch this? I believe we should (?)
>
> I don't think this qualifies as a bug. The current wording isn't
> factually wrong, just unhelpful. Even if it were wrong, we need a
> pretty good reason to change message strings in a stable branch,
> because that can break things for users who are grepping for the
> current string (or a translation thereof). If an overwhelming
> consensus in favor of back-patching emerges, fine, but my gut feeling
> is that back-patching will make more people sad than it makes happy.

It's only the HINT part. If I were to grep/search for the message, I
would definitely use the message part.

Christoph

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message torikoshia 2025-04-01 13:57:44 Re: RFC: Logging plan of the running query
Previous Message Melanie Plageman 2025-04-01 13:54:47 Re: Using read stream in autoprewarm