From: Tom Lane <tgl@sss.pgh.pa.us>
To: Keith Browne <tuxedo@deepsky.com>
To: pgsql-bugs@postgresql.org, andrew@supernews.com, "Brian O'Reilly" <fade@deepsky.com>
Subject: Re: BUG #1552: massive performance hit between 7.4 and 8.0.1
Date: Thu, 24 Mar 2005 14:22:22 -0500
Message-ID: <4841.1111692142@sss.pgh.pa.us> (raw)
In-Reply-To: <14846.1111616020@sss.pgh.pa.us>
References: <20050318232102.08FA0F0E5D@svr2.postgresql.org>
<1111567230.11750.596.camel@localhost.localdomain>
<4241C1DF.2020000@deepsky.com>
<slrnd43hta.rhd.andrew+nonews@trinity.supernews.net>
<13841.1111608763@sss.pgh.pa.us>
<4241D7AB.4030607@deepsky.com>
<14846.1111616020@sss.pgh.pa.us>
I wrote:
> ... Maybe we could
> put in a hack that detects whether a table has yet been vacuumed, and
> sets 10/1000 as the minimum stats --- not fixed values, but minimum
> values that can be overridden when the table is actually larger ---
> until it has been vacuumed.
For lack of any better suggestions, I've done this in HEAD and 8.0
branches. It proved simplest to just limit the page estimate to be
at least 10 pages when relpages == 0. The tuple estimate will be
derived from that using pre-existing code that estimates the average
tuple size.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: tgl@sss.pgh.pa.us, tuxedo@deepsky.com, fade@deepsky.com
Subject: Re: BUG #1552: massive performance hit between 7.4 and 8.0.1
In-Reply-To: <4841.1111692142@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox