From: | Bertrand Drouvot <bertranddrouvot(dot)pg(at)gmail(dot)com> |
---|---|
To: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
Cc: | jian he <jian(dot)universality(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: confusing message in check_tuple |
Date: | 2025-06-18 09:46:51 |
Message-ID: | aFKLC+wJESsP5+hM@ip-10-97-1-34.eu-west-3.compute.internal |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi,
On Tue, Jun 17, 2025 at 07:21:13AM +0200, Peter Eisentraut wrote:
> On 12.06.25 08:26, jian he wrote:
> > in contrib/amcheck/verify_heapam.c, check_tuple
> > report_corruption(ctx,
> > psprintf("number of attributes %u exceeds
> > maximum expected for table %u",
> > ctx->natts,
> > RelationGetDescr(ctx->rel)->natts));
>
> Agreed this is misleading.
>
> > i think it should be
> > report_corruption(ctx,
> > psprintf("number of attributes %u exceeds
> > maximum expected for table %u",
> > ctx->natts,
> > RelationGetRelid(ctx->rel)));
> >
> > or we can rephrase it another way, also mentioning
> > ``RelationGetDescr(ctx->rel)->natts``.
>
> I think they did want to mention RelationGetDescr(ctx->rel)->natts.
+1, I think that we usually want to be able to compare actual vs expected.
> How
> about
>
> "number of attributes %u exceeds maximum expected for table (%u)"
I thought about adding the table name in the message but it looks like it's already
there:
"
Expected corruption message output stdout /(?^:(?^ms:heap table "postgres\.public\.test", block 0, offset 9:\s+)number of attributes 2047 exceeds maximum expected for table 3)
"
So that your proposal makes sense to me.
Regards,
--
Bertrand Drouvot
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com
From | Date | Subject | |
---|---|---|---|
Next Message | shveta malik | 2025-06-18 09:52:59 | Re: POC: enable logical decoding when wal_level = 'replica' without a server restart |
Previous Message | Peter Eisentraut | 2025-06-18 09:44:22 | Re: [PATCH] Add an ldflags_sl meson build option |