From: Gary Doades <gpd@gpdnet.co.uk>
To: pgsql-performance@postgresql.org
Subject: Re: Caching of Queries
Date: Thu, 23 Sep 2004 07:36:11 +0100
Message-ID: <41527CEB.18344.26EF6F28@localhost> (raw)
In-Reply-To: <18410.1095883147@sss.pgh.pa.us>
References: <b3dc511704092212502a2ddb09@mail.gmail.com>
On 22 Sep 2004 at 15:59, Tom Lane wrote:
> Scott Kirkwood <scottakirkwood@gmail.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.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: gpd@gpdnet.co.uk
Subject: Re: Caching of Queries
In-Reply-To: <41527CEB.18344.26EF6F28@localhost>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox