Skip site navigation (1) Skip section navigation (2)

Re: Query cache import?

From: Karel Zak <zakkr(at)zf(dot)jcu(dot)cz>
To: Alfred Perlstein <bright(at)wintelcom(dot)net>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Query cache import?
Date: 2000-11-01 09:52:51
Message-ID: Pine.LNX.3.96.1001101103137.8318A-100000@ara.zf.jcu.cz (view raw or flat)
Thread:
Lists: pgsql-hackers
On Tue, 31 Oct 2000, Alfred Perlstein wrote:

> * Karel Zak <zakkr(at)zf(dot)jcu(dot)cz> [001031 16:18] wrote:
> > 
> > On Tue, 31 Oct 2000, Alfred Perlstein wrote:
> > 
> >  All what will doing next time not depend on me, *it's on code developers*.
							    ^^^^^^^^
						right is "core"

> Well I'm just hoping that perl's $dbh->prepare() actually does a
> temporary stored proceedure so that I can shave cycles off of 
> my thousands upon thousands of repeated queries. :)

 IMHO implement good cache for planns is not easy, if is wanted
use cached planns in more backend and store it in shared memory. I
wrote for this new memory context type. My idea is not save/share 
parsed planns only for PREPARE/EXECUTE statemment but for SPI 
(triggers - FK for example) too. It expect support inside backend
and not is possible write it in some application layout (at client).

 But it's very good "investment", because query pasring in the PG is
very expensive (all in queries is dynamic). In my tests is execute
for stored planns very faster (90%) for queries that spending more time
in the parser/planner/rewriter.

							Karel


In response to

pgsql-hackers by date

Next:From: Frank JoerdensDate: 2000-11-01 10:08:32
Subject: Re: Query caching
Previous:From: Denis PerchineDate: 2000-11-01 09:23:08
Subject: Re: Query caching

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group