From: | The Hermit Hacker <scrappy(at)hub(dot)org> |
---|---|
To: | Karel Zak - Zakkr <zakkr(at)zf(dot)jcu(dot)cz> |
Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [HACKERS] Cache query (PREPARE/EXECUTE) |
Date: | 2000-02-22 16:27:40 |
Message-ID: | Pine.BSF.4.21.0002221223460.86931-100000@thelab.hub.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, 22 Feb 2000, Karel Zak - Zakkr wrote:
> The queryTree and planTree are save in hash table and in the
> TopMemoryContext (Is it good space for this cache?). All is
> without change-schema detection (IMHO is user problem if he
> changes DB schema and use old cached plan). In future I try
Just curious, but a new 'PREPARE name AS...' with the same name just
overrides the previously saved plan?
Actually, can someone who may know the internals of DBI comment on
this? If I have a CGI that runs the same SELECT call each and every time,
this would come in handy ... but how does DBI do its prepare? Would it
set a new name for each invocation, so you would have several 'cached
plans' for the exact same SELECT call?
Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy
Systems Administrator @ hub.org
primary: scrappy(at)hub(dot)org secondary: scrappy(at){freebsd|postgresql}.org
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2000-02-22 16:32:51 | Re: [HACKERS] TRANSACTIONS |
Previous Message | Bruce Momjian | 2000-02-22 16:24:10 | Re: [HACKERS] Beta for 4:30AST ... ? |