Re: updated qCache - Mailing list pgsql-hackers

From Dann Corbit
Subject Re: updated qCache
Date
Msg-id D90A5A6C612A39408103E6ECDD77B82920CD6A@voyager.corporate.connx.com
Whole thread Raw
In response to updated qCache  (Neil Conway <nconway@klamath.dyndns.org>)
Responses Re: updated qCache  (Neil Conway <nconway@klamath.dyndns.org>)
List pgsql-hackers
-----Original Message-----
From: Neil Conway [mailto:nconway@klamath.dyndns.org]
Sent: Wednesday, April 17, 2002 2:18 PM
To: PostgreSQL Hackers
Subject: [HACKERS] updated qCache


Hi all,

Here's an updated version of the experimental qCache patch I
posted a couple days ago (which is a port of Karel Zak's 7.0
work to CVS HEAD).

Changes:

- fix segfault in EXECUTE under some circumstances (reported by Barry Lind)
- fix some memory leaks  (thanks to Karel Zak)
- write more regression tests (make check still won't pass)
- re-diff against CVS HEAD
- more code cleanup, minor tweaks

However, I've tentatively decided that I think the best
way to go forward is to rewrite this code. IMHO the utility of
plans cached in shared memory is fairly limited, but the
code that implements this adds a lot of complex to the patch.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
DC% Why do you imagine that the utility is limited?
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

I'm planning to re-implement PREPARE/EXECUTE with support only
for locally-prepared plans, using the existing patch as a
guide. The result should be a simpler patch -- once it's
in CVS we can worry about more advanced plan caching
techiques. Any complaints/comments on this plan?
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
DC% Why not allow both kinds and make it configurable...
DC% local/shared/both.
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<


pgsql-hackers by date:

Previous
From: Neil Conway
Date:
Subject: updated qCache
Next
From: Bruce Momjian
Date:
Subject: Re: Index Scans become Seq Scans after VACUUM ANALYSE