Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
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: Tue, 31 Jan 2006 21:25:06 -0500
- Message-id: <1138760706(dot)27327(dot)167(dot)camel(at)home>
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. --
- Follow-Ups:
- Re: Tab completion of SET TRANSACTION ISOLATION
- From: Christopher Kings-Lynne
- Re: Tab completion of SET TRANSACTION ISOLATION
- References:
- Re: Tab completion of SET TRANSACTION ISOLATION
- From: Bruce Momjian
- Re: Tab completion of SET TRANSACTION ISOLATION
- Prev by Date: Re: Tab completion of SET TRANSACTION ISOLATION
- Next by Date: Re: Tab completion of SET TRANSACTION ISOLATION
- Previous by thread: Re: Tab completion of SET TRANSACTION ISOLATION
- Next by thread: Re: Tab completion of SET TRANSACTION ISOLATION
- Indexes: