Re: pgstattuple: Have pgstattuple_approx accept TOAST tables

From: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
To: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pgstattuple: Have pgstattuple_approx accept TOAST tables
Date: 2020-06-29 23:14:31
Message-ID: 21566b5e-eb36-bffd-9cd0-1dd5ea2e5e46@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2020-06-17 13:39, Laurenz Albe wrote:
> On Fri, 2020-04-17 at 13:01 +0200, Peter Eisentraut wrote:
>> I alluded to this in [0], but it's better discussed in its own thread.
>>
>> I think the check that makes pgstattuple_approx reject TOAST tables is a
>> mistake. They have visibility and free space map, and it works just
>> fine if the check is removed.
>>
>> Attached is a patch to fix this and add some tests related to how
>> pgstattuple and pg_visibility accept TOAST tables for inspection.
>>
>>
>> [0]:
>> https://www.postgresql.org/message-id/dc35a398-37d0-75ce-07ea-1dd71d98f8ec@2ndquadrant.com
>
> I gave the patch a spin, and it passes regression tests and didn't
> cause any problems when I played with it.
>
> No upgrade or dump considerations, of course.
>
> This is a clear improvement.
>
> I'll mark the patch as "ready for committer".

committed, thanks

--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message David Rowley 2020-06-29 23:22:02 Re: Open Item: Should non-text EXPLAIN always show properties?
Previous Message Andres Freund 2020-06-29 23:10:15 Re: track_planning causing performance regression