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.
---------------------------------------------------------------------------
>
> Peter Eisentraut wrote:
> > 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. It's not a major issue, but
> > I figured I'd mention it since it confused me a while ago. If someone has an
> > ingenious plan for working around this, let me know.
> >
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 2: Don't 'kill -9' the postmaster
>
--
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
In response to
Responses
pgsql-hackers by date
| Next: | From: Rod Taylor | Date: 2006-02-01 01:32:42 |
| Subject: Re: Tab completion of SET TRANSACTION ISOLATION |
| Previous: | From: Christopher Kings-Lynne | Date: 2006-02-01 01:15:47 |
| Subject: Re: Tab completion of SET TRANSACTION ISOLATION |