Re: [PATCH] pg_statio_all_tables: several rows per table due to invalid TOAST index

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andrei Zubkov <zubkov(at)moonset(dot)ru>
Cc: Michael Paquier <michael(at)paquier(dot)xyz>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: [PATCH] pg_statio_all_tables: several rows per table due to invalid TOAST index
Date: 2022-03-24 20:34:13
Message-ID: 3144503.1648154053@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

I wrote:
> After a bit of further fooling, I found that we could make that
> work with LEFT JOIN LATERAL. This formulation has a different
> problem, which is that if you do want most or all of the output,
> computing each sub-aggregation separately is probably less
> efficient than it could be. But this is probably the better way
> to go unless someone has an even better idea.

Hearing no better ideas, pushed.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2022-03-24 20:34:35 Re: identifying unrecognized node type errors
Previous Message Nathan Bossart 2022-03-24 20:31:08 Re: Estimating HugePages Requirements?