Re: 8.3.0 Core with concurrent vacuum fulls - Mailing list pgsql-hackers

From Pavan Deolasee
Subject Re: 8.3.0 Core with concurrent vacuum fulls
Date
Msg-id 2e78013d0803070122v5ee2a2c6l610c01699ca0c0cb@mail.gmail.com
Whole thread Raw
In response to Re: 8.3.0 Core with concurrent vacuum fulls  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: 8.3.0 Core with concurrent vacuum fulls  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Thu, Mar 6, 2008 at 11:30 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:

>
>  I think that just makes things more complex and fragile.  I like
>  Heikki's idea, in part because it makes the normal path and the WAL
>  recovery path guaranteed to work alike.  I'll attach my work-in-progress
>  patch for this --- it doesn't do anything about the invalidation
>  semantics problem but it does fix the critical-section-too-big problem.
>

The WIP patch looks good to me. I haven't yet tested it (will wait for the
final version). The following pointer arithmetic caught my eye though.

!   nunused = (end - nowunused);

Shouldn't we typecast them to (char *) first ?

Thanks,
Pavan

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


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Doubt in heap_release_fetch
Next
From: Hannu Krosing
Date:
Subject: Re: Nasty bug in heap_page_prune