Re: pg_receivexlog always handles -d option argument as connstr

From: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
To: Sawada Masahiko <sawada(dot)mshk(at)gmail(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_receivexlog always handles -d option argument as connstr
Date: 2014-10-07 03:58:49
Message-ID: CAA4eK1KOhBex7vtKPhQnBq4zTiF7Yi4YJEH=q6ez2yU2ZhMCrw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Oct 6, 2014 at 10:23 PM, Sawada Masahiko <sawada(dot)mshk(at)gmail(dot)com>
wrote:
>
> Hi all,
>
> pg_receivexlog always handles argument of -d option as connstr formatted
value.
> We can doubly specify host name, port number.
> The other client tools handles -d option as connstr value only if
> argument has "=" character.

pg_basebackup also seems to behave same as pg_receivexlog.
psql also treats it in similar way. The behaviour of psql is as
below:
psql.exe -d="host=localhost port=5432 dbname=postgres"
psql: invalid connection option ""

psql.exe -d "host=localhost port=5432 dbname=postgres"
psql (9.5devel)
WARNING: Console code page (437) differs from Windows code page (1252)
8-bit characters might not work correctly. See psql reference
page "Notes for Windows users" for details.
Type "help" for help.

postgres=#

> The document says that pg_receivexlog ignores database name, and this
> option is called for consistency with other client applications.
> But if we specify database name like other client tool '-d hoge' ,
> then we will definitely got error.

What I understand from document is that it ignores database name
when given in connection string.

With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2014-10-07 04:07:09 Re: TAP test breakage on MacOS X
Previous Message Peter Geoghegan 2014-10-07 02:31:19 Re: Promise index tuples for UPSERT