From: | Gregory Stark <stark(at)enterprisedb(dot)com> |
---|---|
To: | "Jim C(dot) Nasby" <decibel(at)decibel(dot)org> |
Cc: | "pgsql-patches" <pgsql-patches(at)postgresql(dot)org> |
Subject: | Re: Concurrent psql patch |
Date: | 2007-05-14 14:29:05 |
Message-ID: | 871whjcwcu.fsf@oxford.xeocode.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
"Jim C. Nasby" <decibel(at)decibel(dot)org> writes:
> Would \c# limit us to 9 concurrent connections? Might want
>
> \cs[witch] [session]
Hm, we kind of have a choice with \c#. Either we treat it as part of the
command in which case the way to connect to an integer-named database is to
include a space. We could even have it magically connect to a database if the
connection isn't already active.
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.
Or we treat it as the first argument in which case even "\c 9" switches to
session 9. I would prefer to do that but I fear there may be people with
databases named "9".
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Aidan Van Dyk | 2007-05-14 14:40:48 | Re: What is happening on buildfarm member baiji? |
Previous Message | Tom Lane | 2007-05-14 14:20:39 | Re: What is happening on buildfarm member baiji? |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2007-05-14 15:03:52 | Re: Concurrent psql patch |
Previous Message | Greg Smith | 2007-05-14 13:57:28 | Re: Automatic adjustment of bgwriter_lru_maxpages |