Re: Optimizing count(), but Explain estimates wildly off - Mailing list pgsql-performance

From Greg Sabino Mullane
Subject Re: Optimizing count(), but Explain estimates wildly off
Date
Msg-id CAKAnmmJ2A15dr4XUKF3A=a_Z2VryHPoZSMRvJYZmrsKKuiuYMw@mail.gmail.com
Whole thread Raw
In response to Re: Optimizing count(), but Explain estimates wildly off  (Chema <chema@interneta.org>)
Responses Re: Optimizing count(), but Explain estimates wildly off
List pgsql-performance
On Mon, Mar 4, 2024 at 2:14 PM Chema <chema@interneta.org> wrote:
There's one JSON column in each table with a couple fields, and a column with long texts  in Items.
and earlier indicated the query was:
Select * from tenders inner join items
 
You do not want to do a "select star" on both tables unless you 100% need every single column and plan to actively do something with it. Especially true for large text and json columns. Also, use jsonb not json.

Cheers,
Greg

pgsql-performance by date:

Previous
From: Chema
Date:
Subject: Re: Optimizing count(), but Explain estimates wildly off
Next
From: sud
Date:
Subject: Re: Is partition pruning impacted by data type