From: | mark(at)mark(dot)mielke(dot)cc |
---|---|
To: | Anon Mous <soundami(at)yahoo(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Postgresql Caching |
Date: | 2006-10-15 14:40:13 |
Message-ID: | 20061015144012.GA16852@mark.mielke.cc |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sun, Oct 15, 2006 at 03:41:25AM -0700, Anon Mous wrote:
> However, the problem is surmountable and has been figured out by Oracle,
> although I don't know how they did it:
>
> http://www.oracle.com/technology/products/ias/joc/index.html
I'm pretty sure this is application-side caching. The application is
able to cache intelligently and efficiently, as it is able to make
assumptions. It's only seeing one view of the data. The view is
internally consistent, and only the application is making changes
to the view that it sees.
On the rest of your thinking:
Are people comfortable in believing that tables that do not change
are a valuable point to consider for caching?
Cheers,
mark
--
mark(at)mielke(dot)cc / markm(at)ncf(dot)ca / markm(at)nortel(dot)com __________________________
. . _ ._ . . .__ . . ._. .__ . . . .__ | Neighbourhood Coder
|\/| |_| |_| |/ |_ |\/| | |_ | |/ |_ |
| | | | | \ | \ |__ . | | .|. |__ |__ | \ |__ | Ottawa, Ontario, Canada
One ring to rule them all, one ring to find them, one ring to bring them all
and in the darkness bind them...
From | Date | Subject | |
---|---|---|---|
Next Message | Merlin Moncure | 2006-10-15 15:01:36 | Re: Postgresql Caching |
Previous Message | Anon Mous | 2006-10-15 10:41:25 | Postgresql Caching |