Re: [HACKERS] ANALYZE getting dead tuple count hopelessly wrong - Mailing list pgsql-general

From Pavan Deolasee
Subject Re: [HACKERS] ANALYZE getting dead tuple count hopelessly wrong
Date
Msg-id 2e78013d0803311134v44604be5l20e97ee7d3461ec4@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] ANALYZE getting dead tuple count hopelessly wrong  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [HACKERS] ANALYZE getting dead tuple count hopelessly wrong
List pgsql-general
On Mon, Mar 31, 2008 at 9:02 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:

>
>  [ Please see if you can stop using the "redirected dead" terminology ]
>
>

Apologies, will keep that in mind. Seems like a hang-over from the past :-)

>  Yeah, I think I agree.  The page pruning code is set up so that changing
>  a line pointer to DEAD state doesn't change the count of dead tuples in
>  the table, so we are counting unreclaimed DEAD pointers as still being
>  dead tuples requiring VACUUM.  ANALYZE should surely not affect that.
>
>  It looks like there's no trivial way to get ANALYZE to do things that
>  way, though.  heap_release_fetch() doesn't distinguish a DEAD line
>  pointer from an unused or redirected one.  But in the current
>  implementation of ANALYZE there's really no benefit to using
>  heap_release_fetch anyway --- it always examines all line pointers
>  on each selected page, so we might as well rewrite it to use a simple
>  loop more like vacuum uses.
>

I agree. I would write a patch on these lines, unless you are already on to it.


Thanks,
Pavan

--
Pavan Deolasee
EnterpriseDB http://www.enterprisedb.com

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: Can Postgres 8.x start if some disks containing tablespaces are not mounted?
Next
From: "Just Someone"
Date:
Subject: Re: Very slow catalog query