Re: Modernize error message for malformed B-Tree tuple posting

From: Andrey Borodin <x4mmm(at)yandex-team(dot)ru>
To: Kirill Reshke <reshkekirill(at)gmail(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Modernize error message for malformed B-Tree tuple posting
Date: 2026-03-01 04:46:31
Message-ID: C49B4C2D-FCBE-42B0-804F-082A202658E6@yandex-team.ru
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On 27 Feb 2026, at 17:31, Andrey Borodin <x4mmm(at)yandex-team(dot)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.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Pavel Stehule 2026-03-01 05:44:17 Re: POC: PLpgSQL FOREACH IN JSON ARRAY
Previous Message Tender Wang 2026-03-01 04:14:40 Re: [BUG?] estimate_hash_bucket_stats uses wrong ndistinct for avgfreq