Skip site navigation (1) Skip section navigation (2)

Re: [GENERAL] ANALYZE getting dead tuple count hopelessly wrong

From: "Pavan Deolasee" <pavan(dot)deolasee(at)gmail(dot)com>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [GENERAL] ANALYZE getting dead tuple count hopelessly wrong
Date: 2008-04-03 16:12:48
Message-ID: 2e78013d0804030912j3f6ed6bcxf5a1048630d79981@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-generalpgsql-hackers
On Thu, Apr 3, 2008 at 4:34 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

>
>  The right way seems to be to treat our own insertions as live during
>  ANALYZE, but then subtract off our own pending insertions from the
>  live-tuples count sent to the stats collector.  pgstat_report_analyze()
>  can handle the latter part by groveling through the backend's pending
>  statistics data.
>

Seems like a right approach to me. I assume we shall do the same for
DELETE_IN_PROGRESS tuples.

Thanks,
Pavan

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

In response to

pgsql-hackers by date

Next:From: Svenne KrapDate: 2008-04-03 16:14:17
Subject: Re: [GENERAL] SHA1 on postgres 8.3
Previous:From: Brendan JurdDate: 2008-04-03 16:10:26
Subject: Re: printTable API (was: Show INHERIT in \du)

pgsql-general by date

Next:From: Svenne KrapDate: 2008-04-03 16:14:17
Subject: Re: [GENERAL] SHA1 on postgres 8.3
Previous:From: Peter EisentrautDate: 2008-04-03 16:00:41
Subject: Re: modules

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group