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

Peripheral Links

Header And Logo

PostgreSQL
| The world's most advanced open source database.

Site Navigation

Search for
  Advanced Search

Re: Tab completion of SET TRANSACTION ISOLATION


  • From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
  • To: Rod Taylor <pg(at)rbt(dot)ca>
  • 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 20:53:39 -0500 (EST)
  • Message-id: <200602010153(dot)k111rdl27881(at)candle(dot)pha(dot)pa(dot)us>

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?

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



Home | Main Index | Thread Index

Privacy Policy | PostgreSQL Archives hosted by Command Prompt, Inc. | Designed by tinysofa
Copyright © 1996 – 2008 PostgreSQL Global Development Group