Re: have SLRU truncation use callbacks - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: have SLRU truncation use callbacks
Date
Msg-id 1317748567-sup-1166@alvh.no-ip.org
Whole thread Raw
In response to Re: have SLRU truncation use callbacks  ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>)
List pgsql-hackers
Excerpts from Kevin Grittner's message of jue sep 29 14:51:38 -0300 2011:
> Alvaro Herrera <alvherre@alvh.no-ip.org> wrote:
>  
> > But I think these changes stand on their own, merely on code
> > clarity grounds).
>  
> After a quick scan, I think it helps with that.  This was a messy
> area to deal with in SSI given the old API; with this change I think
> we could make that part of the SSI code clearer and maybe clean up
> unneeded files in a couple places where cleanup under the old API
> was judged not to be worth the code complexity needed to make it
> happen.

Thanks for the review.  I just pushed this.  Note I didn't touch the
predicate.c stuff at all -- I leave that to you, if you're so inclined :-)

-- 
Álvaro Herrera <alvherre@commandprompt.com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support


pgsql-hackers by date:

Previous
From: Dimitri Fontaine
Date:
Subject: Re: Should we get rid of custom_variable_classes altogether?
Next
From: Alex Hunsaker
Date:
Subject: Re: Re: [COMMITTERS] pgsql: Force strings passed to and from plperl to be in UTF8 encoding.