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 01:32:42
Message-ID: 1138757562.27327.161.camel@home (view raw or flat)
Thread:
Lists: pgsql-hackers
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?
-- 


In response to

Responses

pgsql-hackers by date

Next:From: Bruce MomjianDate: 2006-02-01 01:53:39
Subject: Re: Tab completion of SET TRANSACTION ISOLATION
Previous:From: Bruce MomjianDate: 2006-02-01 01:18:33
Subject: Re: Tab completion of SET TRANSACTION ISOLATION

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