Re: [COMMITTERS] pgsql: Fix pg_dumpall with database names containing =

From: Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>
To: Thom Brown <thom(at)linux(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org>
Subject: Re: [COMMITTERS] pgsql: Fix pg_dumpall with database names containing =
Date: 2013-02-27 12:54:53
Message-ID: 512E021D.1050109@vmware.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

On 27.02.2013 11:52, Thom Brown wrote:
> Once I'm in that database, I can't switch user from within psql:
>
> 8=8=# \c - moo
> invalid connection option "8"
> Previous connection kept

Hmm, true. Also, any other connection options you specified in the
original connection string are lost. For example, if you first connected
with:

psql "dbname=foo sslmode=require"

and then did "\c - anotheruser", the second connection would not require
ssl.

- Heikki

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message fxjr 2013-02-27 13:06:40 npgsql - Npgsql2: [#1011310] Command timeouts after the first are not
Previous Message Thom Brown 2013-02-27 09:52:38 Re: pgsql: Fix pg_dumpall with database names containing =

Browse pgsql-hackers by date

  From Date Subject
Next Message Heikki Linnakangas 2013-02-27 13:00:04 Re: Review : Add hooks for pre- and post-processor executables for COPY and \copy
Previous Message Michael Meskes 2013-02-27 11:33:44 Re: "COPY foo FROM STDOUT" and ecpg