Re: [GENERAL] ANALYZE getting dead tuple count hopelessly wrong - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [GENERAL] ANALYZE getting dead tuple count hopelessly wrong
Date
Msg-id 2320.1207062015@sss.pgh.pa.us
Whole thread Raw
In response to Re: [GENERAL] ANALYZE getting dead tuple count hopelessly wrong  (Simon Riggs <simon@2ndquadrant.com>)
List pgsql-hackers
Simon Riggs <simon@2ndquadrant.com> writes:
> On Tue, 2008-04-01 at 10:22 -0400, Tom Lane wrote:
>> In the fourth, if we actually believed this was a problem we'd
>> need to redesign VACUUM too, as it does the same thing.

> VACUUM waits until nobody else has the buffer pinned, so lock contention
> is much less of a consideration there. Plus it rearranges the block,
> which is hard to do one tuple at a time even if we wanted to.

That's the second scan.  The first scan acts exactly like Pavan is
proposing for ANALYZE.

            regards, tom lane

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Scroll cursor oddity...
Next
From: Mathias Hasselmann
Date:
Subject: Re: [PATCHES] Avahi support for Postgresql