From: | "Gary Doades" <gpd(at)gpdnet(dot)co(dot)uk> |
---|---|
To: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: Caching of Queries |
Date: | 2004-09-23 06:36:11 |
Message-ID: | 41527CEB.18344.26EF6F28@localhost |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On 22 Sep 2004 at 15:59, Tom Lane wrote:
> Scott Kirkwood <scottakirkwood(at)gmail(dot)com> writes:
> > What do you think?
>
> I think this would allow the problems of cached plans to bite
> applications that were previously not subject to them :-(.
> An app that wants plan re-use can use PREPARE to identify the
> queries that are going to be re-executed.
>
> regards, tom lane
>
And then there are the people that would like to upgrade and get a
performance gain without having to change their programs. A simple
conf flag could turn query/plan caching off for all those that rely on each
statement being re-planned.
This is where SQLServer etc. tend to get big wins. I know from direct
comparisons that SQLServer often takes quite a bit longer to parse/plan
a select statement than Postgres, but wins out overall from its
query/plan caching.
Regards,
Gary.
From | Date | Subject | |
---|---|---|---|
Next Message | Gaetano Mendola | 2004-09-23 08:52:21 | Re: Caching of Queries |
Previous Message | Neil Conway | 2004-09-23 03:58:34 | Re: O_DIRECT setting |