Re: bug in pageinspect's "tuple data" feature - Mailing list pgsql-hackers

From Heikki Linnakangas
Subject Re: bug in pageinspect's "tuple data" feature
Date
Msg-id 687d533e-8bba-ef70-68bf-ca56182fb507@iki.fi
Whole thread Raw
In response to bug in pageinspect's "tuple data" feature  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
Responses Re: bug in pageinspect's "tuple data" feature  (Michael Paquier <michael@paquier.xyz>)
List pgsql-hackers
On 21/11/2020 21:32, Alvaro Herrera wrote:
> If you have a sufficiently broken data page, pageinspect throws an
> error when trying to examine the page:
> 
> ERROR:  invalid memory alloc request size 18446744073709551451
> 
> This is pretty unhelpful; it would be better not to try to print the
> data instead of dying.  With that, at least you can know where the
> problem is.
> 
> This was introduced in d6061f83a166 (2015).  Proposed patch to fix it
> (by having the code print a null "data" instead of dying) is attached.

Null seems misleading. Maybe something like "invalid", or print a warning?

- Heikki



pgsql-hackers by date:

Previous
From: Bharath Rupireddy
Date:
Subject: Re: [PATCH] postgres_fdw connection caching - cause remote sessions linger till the local session exit
Next
From: Andrey Lepikhov
Date:
Subject: Re: [POC] Fast COPY FROM command for the table with foreign partitions