Skip site navigation (1) Skip section navigation (2)

Re: Tab completion of SET TRANSACTION ISOLATION

From: Rod Taylor <pg(at)rbt(dot)ca>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>, Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Tab completion of SET TRANSACTION ISOLATION
Date: 2006-02-01 02:25:06
Message-ID: 1138760706.27327.167.camel@home (view raw or flat)
Thread:
Lists: pgsql-hackers
On Tue, 2006-01-31 at 20:53 -0500, Bruce Momjian wrote:
> Rod Taylor wrote:
> > On Tue, 2006-01-31 at 20:18 -0500, Bruce Momjian wrote:
> > > Christopher Kings-Lynne wrote:
> > > > It could read all the SET variables in at startup?
> > > 
> > > Right, but do we want to do that even if they never ask for a tab
> > > completion?  I think the easiest might be to just save the list on first
> > > tab call.
> > 
> > As mentioned earlier the problem exists for all tab completion in
> > aborted transactions.
> > 
> > Perhaps a second database connection could be established during
> > situations when running tab completion and other psql commands is
> > impossible on the main one?
> 
> What if you need a password to be supplied?

I believe psql keeps the password in memory.

\c seems to be able to change databases without asking for the password
again.

-- 


In response to

Responses

pgsql-hackers by date

Next:From: Christopher Kings-LynneDate: 2006-02-01 02:28:15
Subject: Re: Tab completion of SET TRANSACTION ISOLATION
Previous:From: Neil ConwayDate: 2006-02-01 02:17:51
Subject: Re: Tab completion of SET TRANSACTION ISOLATION

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group