From: | Magnus Hagander <magnus(at)hagander(dot)net> |
---|---|
To: | Alexander Korotkov <aekorotkov(at)gmail(dot)com> |
Cc: | Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Idea: Always consistent in-database cache using SSI mechanisms |
Date: | 2011-10-25 11:42:40 |
Message-ID: | CABUevEzGNRgZJ2PhHch-wp+Ce5xcHgnLQ3eb-9ZzpjuGMBbbug@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Oct 25, 2011 at 00:00, Alexander Korotkov <aekorotkov(at)gmail(dot)com> wrote:
> On Tue, Oct 25, 2011 at 1:46 AM, Kevin Grittner
> <Kevin(dot)Grittner(at)wicourts(dot)gov> wrote:
>>
>> Alexander Korotkov <aekorotkov(at)gmail(dot)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/
From | Date | Subject | |
---|---|---|---|
Next Message | Fujii Masao | 2011-10-25 11:54:58 | Re: Online base backup from the hot-standby |
Previous Message | Florian Pflug | 2011-10-25 11:39:39 | Re: Hot Backup with rsync fails at pg_clog if under load |