Re: Idea: Always consistent in-database cache using SSI mechanisms - Mailing list pgsql-hackers

From Magnus Hagander
Subject Re: Idea: Always consistent in-database cache using SSI mechanisms
Date
Msg-id CABUevEzGNRgZJ2PhHch-wp+Ce5xcHgnLQ3eb-9ZzpjuGMBbbug@mail.gmail.com
Whole thread Raw
In response to Re: Idea: Always consistent in-database cache using SSI mechanisms  (Alexander Korotkov <aekorotkov@gmail.com>)
List pgsql-hackers
On Tue, Oct 25, 2011 at 00:00, Alexander Korotkov <aekorotkov@gmail.com> wrote:
> On Tue, Oct 25, 2011 at 1:46 AM, Kevin Grittner
> <Kevin.Grittner@wicourts.gov> wrote:
>>
>> Alexander Korotkov <aekorotkov@gmail.com> wrote:
>>
>> > Coundn't be predicate locking implementation in SSI be used for
>> > in-database cache invalidation.
>>
>> It would not necessarily be limited to *in-database* caches.  The
>> main thing would be to design a good API to the predicate locking
>> portion of SSI, which I think is about 80% of the SSI code.  Dan and
>> I both have an interest in such further use, and there have been
>> others who have talked about potential uses for the non-blocking
>> predicate locking.  I think the API would need to be based around a
>> listen/notify model.

IIRC, I discussed this with Dan Ports at pgcon, as it was one of the
things he had been looking into as well. You might want to talk to him
about it.

--
 Magnus Hagander
 Me: http://www.hagander.net/
 Work: http://www.redpill-linpro.com/


pgsql-hackers by date:

Previous
From: Florian Pflug
Date:
Subject: Re: Hot Backup with rsync fails at pg_clog if under load
Next
From: Fujii Masao
Date:
Subject: Re: Online base backup from the hot-standby