From: Tom Lane <tgl@sss.pgh.pa.us>
To: Tatsuo Ishii <t-ishii@sra.co.jp>
Cc: matt@ymogen.net
Cc: pg@rbt.ca
Cc: awerman2@hotmail.com
Cc: scottakirkwood@gmail.com
Cc: pgsql-performance@postgresql.org
Subject: Re: Caching of Queries
Date: Wed, 06 Oct 2004 23:12:14 -0400
Message-ID: <23362.1097118734@sss.pgh.pa.us> (raw)
In-Reply-To: <20041007.100847.26272104.t-ishii@sra.co.jp>
References: <20041004.002823.85416338.t-ishii@sra.co.jp>
<012501c4aaf0$f12d0930$8300a8c0@solent>
<20041007.100847.26272104.t-ishii@sra.co.jp>
Tatsuo Ishii <t-ishii@sra.co.jp> writes:
> First, it's not a particular problem with pgpool. As far as I know any
> connection pool solution has exactly the same problem. Second, it's
> easy to fix if PostgreSQL provides a functionarity such as:"drop all
> temporary tables if any".
I don't like that definition exactly --- it would mean that every time
we add more backend-local state, we expect client drivers to know to
issue the right incantation to reset that kind of state.
I'm thinking we need to invent a command like "RESET CONNECTION" that
resets GUC variables, drops temp tables, forgets active NOTIFYs, and
generally does whatever else needs to be done to make the session state
appear virgin. When we add more such state, we can fix it inside the
backend without bothering clients.
I now realize that our "RESET ALL" command for GUC variables was not
fully thought out. We could possibly redefine it as doing the above,
but that might break some applications ...
regards, tom lane
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: tgl@sss.pgh.pa.us, t-ishii@sra.co.jp, matt@ymogen.net, pg@rbt.ca, awerman2@hotmail.com, scottakirkwood@gmail.com
Subject: Re: Caching of Queries
In-Reply-To: <23362.1097118734@sss.pgh.pa.us>
* 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