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

Re: Concurrent psql patch

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Gregory Stark <stark(at)enterprisedb(dot)com>
Cc: "Jim C(dot) Nasby" <decibel(at)decibel(dot)org>, "pgsql-patches" <pgsql-patches(at)postgresql(dot)org>
Subject: Re: Concurrent psql patch
Date: 2007-05-14 15:03:52
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackerspgsql-patches
Gregory Stark <stark(at)enterprisedb(dot)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

In response to


pgsql-hackers by date

Next:From: Tom LaneDate: 2007-05-14 15:28:40
Subject: Re: What is happening on buildfarm member baiji?
Previous:From: Gregory StarkDate: 2007-05-14 15:03:49
Subject: Re: What is happening on buildfarm member baiji?

pgsql-patches by date

Next:From: Jim C. NasbyDate: 2007-05-14 16:41:09
Subject: Re: Have vacuum emit a warning when it runs out of maintenance_work_mem
Previous:From: Gregory StarkDate: 2007-05-14 14:29:05
Subject: Re: Concurrent psql patch

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