Re: [PATCH] pg_statio_all_tables: several rows per table due to invalid TOAST index - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [PATCH] pg_statio_all_tables: several rows per table due to invalid TOAST index
Date
Msg-id 3144503.1648154053@sss.pgh.pa.us
Whole thread Raw
In response to Re: [PATCH] pg_statio_all_tables: several rows per table due to invalid TOAST index  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [PATCH] pg_statio_all_tables: several rows per table due to invalid TOAST index  (Andrei Zubkov <zubkov@moonset.ru>)
List 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



pgsql-hackers by date:

Previous
From: Nathan Bossart
Date:
Subject: Re: Estimating HugePages Requirements?
Next
From: Andrew Dunstan
Date:
Subject: Re: identifying unrecognized node type errors