| From: | Neil Conway <nconway(at)klamath(dot)dyndns(dot)org> |
|---|---|
| To: | "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: experimental pg_qcache patch |
| Date: | 2002-04-14 04:36:38 |
| Message-ID: | 20020414003638.1bee065f.nconway@klamath.dyndns.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sun, 14 Apr 2002 12:11:31 +0800
"Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au> wrote:
> Does it cache all queries or just explicitly prepared ones?
Just explicitly prepared ones. Caching all queries opens a can of
worms that I'd rather not deal with at the moment (volunteers to
tackle this problem are welcome).
>
> Does is check for cached queries all the time or just explicitly EXECUTED
> ones?
A cached query plan is only used for EXECUTE queries -- it is
not used all the time. My gut feeling WRT to caching everything
is similar to my response to your first question.
Cheers,
Neil
--
Neil Conway <neilconway(at)rogers(dot)com>
PGP Key ID: DB3C29FC
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2002-04-14 04:54:46 | Re: [PATCHES] [patch] fe-connect.c doesn't handle EINTR correctly |
| Previous Message | Barry Lind | 2002-04-14 04:16:02 | cost of parse/plan/execute for one sample query |