From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
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 17:16:15 |
Message-ID: | 24214.951239775@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Karel Zak - Zakkr <zakkr(at)zf(dot)jcu(dot)cz> writes:
> as I said, I tring implement PREPARE / EXECUTE command for user a
> controllable query cache (in TODO: Cache most recent query plan(s)).
Looks cool.
> The queryTree and planTree are save in hash table and in the
> TopMemoryContext (Is it good space for this cache?).
Probably not. I'd suggest making a separate memory context for
this purpose --- they're cheap, and that gives you more control.
Look at the creation and use of CacheMemoryContext for an example.
> I'am not sure with syntax, now is:
> PREPARE name AS optimizable-statement [ USING type, ... ]
> EXECUTE name [ USING value, ... ]
> Comments? Suggestions? (SQL92?)
This seems to be quite at variance with SQL92, unfortunately, so it
might not be a good idea to use the same keywords they do...
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Karel Zak - Zakkr | 2000-02-22 17:30:48 | Re: [HACKERS] Cache query (PREPARE/EXECUTE) |
Previous Message | The Hermit Hacker | 2000-02-22 17:16:12 | Re: [HACKERS] PostgreSQL v7.0 goes Beta ... |