Tom Lane <[EMAIL PROTECTED]> writes: > Hm, that's a bit nasty. > > The only plan I can think of involves reading the list of available > variable names in advance and keeping it around. However, I'm not > sure I want psql issuing such a query at connection startup whether > or not the info will ever be used :-(
Well, it could just lazily cache the data if it's ever fetched. That would at least limit the occurrence of this problem to only happening once per connection. psql could also hard code "SET TRANSACTION ISOLATION" specifically. If psql knew that "SET TRANS" completes to SET TRANSACTION and "SET TRANSACTION I" completes to "SET TRANSACTION ISOLATION" it could avoid doing the query at all. That would only fail if someone uses TAB to view the available completions for "SET" or any shorter string. And since transaction isolation is strangely absent from the list of completions that seems like not such a big concern. If he's doing that he's not going to find it anyways. -- greg ---------------------------(end of broadcast)--------------------------- TIP 6: explain analyze is your friend
