Re: Concurrent psql patch

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: Concurrent psql patch
Дата
Msg-id 11752.1179155032@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: Concurrent psql patch  (Gregory Stark <stark@enterprisedb.com>)
Ответы Re: Concurrent psql patch  ("Jim C. Nasby" <decibel@decibel.org>)
Список pgsql-patches
Gregory Stark <stark@enterprisedb.com> writes:
> But these kinds of inconsistent behaviours can be traps for users. It means
> "\c1" and "\c 1" do different things even though "\cpostgres" and \c postgres"
> do the same thing. And it means "\c1" might connect to a database named "1"
> today but switch sessions tomorrow.

The real problem here is trying to overload an existing command name
with too many different meanings.  You need to pick some other name
besides \c.

If you were willing to think of it as "switch session" instead of "connect",
then \S is available ...

            regards, tom lane

В списке pgsql-patches по дате отправления:

Предыдущее
От: Gregory Stark
Дата:
Сообщение: Re: Concurrent psql patch
Следующее
От: "Jim C. Nasby"
Дата:
Сообщение: Re: Have vacuum emit a warning when it runs out of maintenance_work_mem