Re: Cached Query Plans

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: PFC <lists(at)peufeu(dot)com>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Cached Query Plans
Date: 2008-04-11 23:17:27
Message-ID: 18717.1207955847@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

PFC <lists(at)peufeu(dot)com> writes:
> And it is very easy to recognize a query we've seen before,

It's not so easy as all that. Consider search_path. Consider temp
tables.

The real problem here is entirely on the client side:

> But, using prepared statements with persistent connections is messy,
> because you never know if the connection is new or not,

If you were to fix *that* then both this problem and others (such as
setting up desired SET-parameter values) would go away.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Gregory Stark 2008-04-11 23:35:15 Re: Cached Query Plans
Previous Message PFC 2008-04-11 23:05:44 Re: Cached Query Plans