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

Re: Concurrent psql patch

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: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackerspgsql-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

In response to


pgsql-hackers by date

Next:From: Aidan Van DykDate: 2007-05-14 14:40:48
Subject: Re: What is happening on buildfarm member baiji?
Previous:From: Tom LaneDate: 2007-05-14 14:20:39
Subject: Re: What is happening on buildfarm member baiji?

pgsql-patches by date

Next:From: Tom LaneDate: 2007-05-14 15:03:52
Subject: Re: Concurrent psql patch
Previous:From: Greg SmithDate: 2007-05-14 13:57:28
Subject: Re: Automatic adjustment of bgwriter_lru_maxpages

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