Re: Separate psql commands from arguments - Mailing list pgsql-hackers

From Brendan Jurd
Subject Re: Separate psql commands from arguments
Date
Msg-id 37ed240d0804041750i1c943ca7vb0892812c1d9b40@mail.gmail.com
Whole thread Raw
In response to Re: Separate psql commands from arguments  (Gregory Stark <stark@enterprisedb.com>)
Responses Re: Separate psql commands from arguments  (Gregory Stark <stark@enterprisedb.com>)
List pgsql-hackers
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Sat, Apr 5, 2008 at 10:00 AM, Gregory Stark  wrote:
>  Regardless of whether we go ahead with this (and I'm not fond of it primarily
>  because I want \c& to "work"),

Okay, but what on earth is "\c&" and what would you expect it to do
when it "works"?  I suppose you're connecting to a database, but
somehow I don't think you're talking about a database with the name
"&".

If & has some special meaning as a psql argument (and I see no mention
of it in the manual; another undocumented quirk?) then you'd still be
able to do "\c &" ...

Regards,
BJ
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: http://getfiregpg.org

iD8DBQFH9szU5YBsbHkuyV0RAvQkAKCdEM5auZYGDTgoy2h/gRZlaazowgCfePcg
G45rv1TBopMYNl011fuo/XU=
=AZ04
-----END PGP SIGNATURE-----


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Re: [COMMITTERS] pgsql: Implement current_query(), that shows the currently executing
Next
From: Bruce Momjian
Date:
Subject: Re: Patch queue -> wiki