Re: Tab completion of SET TRANSACTION ISOLATION
Rod Taylor <pg@rbt.ca>
From: Rod Taylor <pg@rbt.ca>
To: Bruce Momjian <pgman@candle.pha.pa.us>
Cc: Christopher Kings-Lynne <chriskl@familyhealth.com.au>, Peter Eisentraut <peter_e@gmx.net>, pgsql-hackers@postgresql.org
Date: 2006-02-01T02:25:06Z
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. --