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

Re: Tab completion of SET TRANSACTION ISOLATION

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Tab completion of SET TRANSACTION ISOLATION
Date: 2006-02-01 06:23:34
Message-ID: 26782.1138775014@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackers
Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> Some time ago, the tab completion code for the SET command was changed
> to read the list of available settings from the pg_settings table.
> This means that by the time you're done completing SET TRANSACTION
> ISOLATION, you've already sent a query and the command will be
> disallowed.

Of course, there's always Plan B: revert that patch and go back to
a hard-coded list of variable names.

			regards, tom lane

In response to

pgsql-hackers by date

Next:From: Dave PageDate: 2006-02-01 08:35:51
Subject: FW: PGBuildfarm member snake Branch REL8_0_STABLE Status changed from OK to Make failure
Previous:From: Tom LaneDate: 2006-02-01 05:56:00
Subject: Re: Tab completion of SET TRANSACTION ISOLATION

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