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

From Pavan Deolasee
Subject Re: [GENERAL] ANALYZE getting dead tuple count hopelessly wrong
Date
Msg-id 2e78013d0804030912j3f6ed6bcxf5a1048630d79981@mail.gmail.com
Whole thread Raw
In response to Re: [GENERAL] ANALYZE getting dead tuple count hopelessly wrong  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Thu, Apr 3, 2008 at 4:34 AM, Tom Lane <tgl@sss.pgh.pa.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


pgsql-hackers by date:

Previous
From: "Brendan Jurd"
Date:
Subject: Re: printTable API (was: Show INHERIT in \du)
Next
From: "Tom Dunstan"
Date:
Subject: Re: modules