Re: Row estimates for empty tables

From: Christophe Pettus <xof(at)thebuild(dot)com>
To: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, David Rowley <dgrowleyml(at)gmail(dot)com>, postgre <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: Row estimates for empty tables
Date: 2020-07-24 19:35:35
Message-ID: 733B3ABE-ACF7-4C94-852F-719A46B4BD07@thebuild.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers


> On Jul 24, 2020, at 12:14, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> wrote:
>
> this application stores some results in tables (as guard against repeated calculations). Lot of these tables have zero or one row.

Yes, that's the situation we encountered, too. It's not very common (and even less common, I would assume, that it results in a bad plan), but it did in this case.

--
-- Christophe Pettus
xof(at)thebuild(dot)com

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Adrian Klaver 2020-07-24 20:04:56 Re: when is RLS policy applied
Previous Message Ted Toth 2020-07-24 19:34:48 when is RLS policy applied

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2020-07-24 19:49:14 Re: [PATCH] fix GIN index search sometimes losing results
Previous Message Tomas Vondra 2020-07-24 19:16:48 Re: Default setting for enable_hashagg_disk