Re: [HACKERS] Cache query (PREPARE/EXECUTE)
От | Tom Lane |
---|---|
Тема | Re: [HACKERS] Cache query (PREPARE/EXECUTE) |
Дата | |
Msg-id | 24214.951239775@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Cache query (PREPARE/EXECUTE) (Karel Zak - Zakkr <zakkr@zf.jcu.cz>) |
Ответы |
Re: [HACKERS] Cache query (PREPARE/EXECUTE)
RE: [HACKERS] Cache query (PREPARE/EXECUTE) |
Список | pgsql-hackers |
Karel Zak - Zakkr <zakkr@zf.jcu.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
В списке pgsql-hackers по дате отправления: