Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: [GENERAL] ANALYZE getting dead tuple count hopelessly wrong
- From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
- To: "Pavan Deolasee" <pavan(dot)deolasee(at)gmail(dot)com>
- Cc: "Stuart Brooks" <stuartb(at)cat(dot)co(dot)za>, pgsql-general(at)postgresql(dot)org, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
- Subject: Re: [GENERAL] ANALYZE getting dead tuple count hopelessly wrong
- Date: Mon, 31 Mar 2008 15:52:46 -0400
- Message-id: <19331.1206993166@sss.pgh.pa.us> <text/plain>
"Pavan Deolasee" <pavan(dot)deolasee(at)gmail(dot)com> writes: > On Mon, Mar 31, 2008 at 9:02 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote: >> 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. Please do --- I have a lot of other stuff on my plate. regards, tom lane
- References:
- Re: [GENERAL] ANALYZE getting dead tuple count hopelessly wrong
- From: Pavan Deolasee
- Re: [GENERAL] ANALYZE getting dead tuple count hopelessly wrong
- From: Tom Lane
- Re: [GENERAL] ANALYZE getting dead tuple count hopelessly wrong
- From: Pavan Deolasee
- Re: [GENERAL] ANALYZE getting dead tuple count hopelessly wrong
- Prev by Date: SPI support needed for EXECUTE USING
- Next by Date: Re: POSIX shared memory support
- Previous by thread: Re: [GENERAL] ANALYZE getting dead tuple count hopelessly wrong
- Next by thread: WIP: CASE statement for PL/pgSQL
- Indexes: