pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Bruce Momjian <pgman@candle.pha.pa.us>
To: Tatsuo Ishii <t-ishii@sra.co.jp>
Cc: tgl@sss.pgh.pa.us
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: Tue, 12 Oct 2004 21:02:57 -0400 (EDT)
Message-ID: <200410130102.i9D12vN08023@candle.pha.pa.us> (raw)
In-Reply-To: <20041007.161842.77062117.t-ishii@sra.co.jp>


Added to TODO:

* Add RESET CONNECTION command to reset all session state

  This would include resetting of all variables (RESET ALL), dropping of
  all temporary tables, removal of any NOTIFYs, etc.  This could be used
  for connection pooling.  We could also change RESET ALL to have this
  functionality.


---------------------------------------------------------------------------

Tatsuo Ishii wrote:
> > 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.
> 
> Great. It's much better than I propose.
> 
> > 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
> > 
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 2: you can get off all lists at once with the unregister command
>     (send "unregister YourEmailAddressHere" to majordomo@postgresql.org)
> 

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073



view thread (72+ messages)  latest in thread

Message-ID: <200410130102.i9D12vN08023@candle.pha.pa.us>
Permalink:  ../200410130102.i9D12vN08023@candle.pha.pa.us/
Also on:    postgresql.org/message-id/200410130102.i9D12vN08023@candle.pha.pa.us

 · 

reply

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: pgman@candle.pha.pa.us, t-ishii@sra.co.jp, tgl@sss.pgh.pa.us, matt@ymogen.net, pg@rbt.ca, awerman2@hotmail.com, scottakirkwood@gmail.com
  Subject: Re: Caching of Queries
  In-Reply-To: <200410130102.i9D12vN08023@candle.pha.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