From: Bruce Momjian <bruce@momjian.us>
To: Simon Riggs <simon@2ndQuadrant.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Andrew Dunstan <andrew@dunslane.net>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>
Subject: Re: [PERFORM] encouraging index-only scans
Date: Thu, 13 Dec 2012 08:46:45 -0500
Message-ID: <20121213134645.GA15258@momjian.us> (raw)
In-Reply-To: <CA+U5nMJCDPtL6AkJNRpNzkwq0pEXgOoGNxj7WqOgPVaye5QGtQ@mail.gmail.com>
References: <50C8F1EC.9010801@dunslane.net>
<15321.1355347953@sss.pgh.pa.us>
<50C90154.8060103@dunslane.net>
<50C904DB.9090305@dunslane.net>
<20121213024837.GB22363@momjian.us>
<23298.1355370698@sss.pgh.pa.us>
<CA+U5nMJCDPtL6AkJNRpNzkwq0pEXgOoGNxj7WqOgPVaye5QGtQ@mail.gmail.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>
On Thu, Dec 13, 2012 at 09:40:40AM +0000, Simon Riggs wrote:
> On 13 December 2012 03:51, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>
> >> Yes, this does seem like a problem for upgrades from 9.2 to 9.3? We can
> >> have pg_dump --binary-upgrade set these, or have ANALYZE set it. I
> >> would prefer the later.
> >
> > ANALYZE does not set that value, and is not going to start doing so,
> > because it doesn't scan enough of the table to derive a trustworthy
> > value.
>
> ISTM that ANALYZE doesn't need to scan the table to do this. The
> vismap is now trustworthy and we can scan it separately on ANALYZE.
>
> More to the point, since we run ANALYZE more frequently than we run
> VACUUM, the value stored by the last VACUUM could be very stale.
Wouldn't inserts affect the relallvisible ratio, but not cause a vacuum?
Seems we should be having analyze update this independent of pg_upgrade
needing it. Also, why is this in pg_class?
--
Bruce Momjian <bruce@momjian.us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
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: bruce@momjian.us, simon@2ndQuadrant.com, tgl@sss.pgh.pa.us, andrew@dunslane.net, pgsql-hackers@postgresql.org
Subject: Re: [PERFORM] encouraging index-only scans
In-Reply-To: <20121213134645.GA15258@momjian.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