Re: Database Caching

Sorry, NOTIFY -- not NOTICE (damn keyboard...)

Right now we're required to do a select against the database
periodically which means a test is required before hitting any cached
elements. By the time you select true, might as well do the real
select anyway (normally simple index lookup).

The ability to receive one without making a query first would be very
advantageous.
--
Rod Taylor

This message represents the official view of the voices in my head

----- Original Message -----
From: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Rod Taylor" <rbt(at)zort(dot)ca>
Cc: "Hannu Krosing" <hannu(at)krosing(dot)net>; "Dann Corbit"
<DCorbit(at)connx(dot)com>; "Greg Sabino Mullane" <greg(at)turnstep(dot)com>;
<pgsql-hackers(at)postgresql(dot)org>
Sent: Monday, March 04, 2002 4:50 PM
Subject: Re: [HACKERS] Database Caching

> "Rod Taylor" <rbt(at)zort(dot)ca> writes:
> > Rather than result caching, I'd much rather see an asynchronous
NOTICE
> > telling my webservers which have RULES firing them off when a
table is
> > modified.
>
> LISTEN/NOTIFY?
>
> regards, tom lane
>