Re: PREPARE / EXECUTE

From: Karel Zak <zakkr(at)zf(dot)jcu(dot)cz>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: hs(at)cybertec(dot)at, pgsql-hackers(at)postgresql(dot)org
Subject: Re: PREPARE / EXECUTE
Date: 2002-10-24 06:18:20
Message-ID: 20021024081820.B13536@zf.jcu.cz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Oct 23, 2002 at 11:02:14AM -0400, Tom Lane wrote:
> =?ISO-8859-1?Q?Hans-J=FCrgen_Sch=F6nig?= <postgres(at)cybertec(dot)at> writes:
> > I wonder if there is a way to store a parsed/rewritten/planned query in
> > a table so that it can be loaded again.
>
> The original version of the PREPARE patch used a shared-across-backends
> cache for PREPAREd statements. We rejected that for a number of
> reasons, one being the increased difficulty of keeping such a cache up
> to date. I think actually storing the plans on disk would have all the
> same problems, but worse.

Right.

There's solution: persisten backend (for example like classic
apache). This solve problem with lifetime of all persistent caches.
It's already in TODO.

Karel

--
Karel Zak <zakkr(at)zf(dot)jcu(dot)cz>
http://home.zf.jcu.cz/~zakkr/

C, PostgreSQL, PHP, WWW, http://docs.linux.cz, http://mape.jcu.cz

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Hans-Jürgen Schönig 2002-10-24 08:18:57 Using the same condition twice
Previous Message Marc G. Fournier 2002-10-24 04:18:04 Re: One 7.3 item left