Matthew Peter wrote:
Wouldn't it work just like plpgsql functions? Where the first call caches the
plan
or whatever?
A stored procedure can cache the query plan but that is separate from
caching data.
When sending sql select statements to the server the query plan isn't
cached (if it was
--- Shane Ambler <[EMAIL PROTECTED]> wrote:
> Matthew Peter wrote:
> > --- Willy-Bas Loos <[EMAIL PROTECTED]> wrote:
> >
> >> maybe you would find "materialized views" interesting.
> >> http://www.google.com/search?q=materialized+view+postgresql
> >>
> >>
> >> On 12/1/06, Matthew Peter <[EMAIL P
Matthew Peter wrote:
--- Willy-Bas Loos <[EMAIL PROTECTED]> wrote:
maybe you would find "materialized views" interesting.
http://www.google.com/search?q=materialized+view+postgresql
On 12/1/06, Matthew Peter <[EMAIL PROTECTED]> wrote:
Is it possible to put an query result into memory? Like S
--- Willy-Bas Loos <[EMAIL PROTECTED]> wrote:
> maybe you would find "materialized views" interesting.
> http://www.google.com/search?q=materialized+view+postgresql
>
>
> On 12/1/06, Matthew Peter <[EMAIL PROTECTED]> wrote:
> >
> > Is it possible to put an query result into memory? Like SELECT
maybe you would find "materialized views" interesting.
http://www.google.com/search?q=materialized+view+postgresql
On 12/1/06, Matthew Peter <[EMAIL PROTECTED]> wrote:
Is it possible to put an query result into memory? Like SELECT * from
table WHERE
[...] CACHE cache_name TIMEOUT '1 hour'::int
Matthew Peter wrote:
Is it possible to put an query result into memory? Like SELECT * from table
WHERE
[...] CACHE cache_name TIMEOUT '1 hour'::interval; So if "cache_name" exists
with
the same SQL statement, the result would be fetched from the cache, refreshing
and
updating the cache with fr
