Re: Modernize error message for malformed B-Tree tuple posting - Mailing list pgsql-hackers

From Andrey Borodin
Subject Re: Modernize error message for malformed B-Tree tuple posting
Date
Msg-id C49B4C2D-FCBE-42B0-804F-082A202658E6@yandex-team.ru
Whole thread Raw
In response to Re: Modernize error message for malformed B-Tree tuple posting  (Andrey Borodin <x4mmm@yandex-team.ru>)
List pgsql-hackers

> On 27 Feb 2026, at 17:31, Andrey Borodin <x4mmm@yandex-team.ru> wrote:
> 
> elog(ERROR, "fell off the end of index \"%s\"",
> elog(ERROR, "no live root page found in index \"%s\"",
> elog(ERROR, "root page %u of index \"%s\" has level %u, expected %u",
> 
> are of the same kind, but I do not remember seeing them on production.

I think 8ec97e78 and fd6ec93 established that we use error codes
when an error is potentially reachable. And so far we do not have evidence
for these cases. So, no need to change this.


Best regards, Andrey Borodin.



pgsql-hackers by date:

Previous
From: Tender Wang
Date:
Subject: Re: [BUG?] estimate_hash_bucket_stats uses wrong ndistinct for avgfreq
Next
From: Pavel Stehule
Date:
Subject: Re: POC: PLpgSQL FOREACH IN JSON ARRAY