| From: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(dot)net> |
| Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pg_basebackup for streaming base backups |
| Date: | 2011-01-17 13:43:57 |
| Message-ID: | AANLkTikRxKMb5KMK26GcKfA+ytNjqMboE--JGNPRThOo@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Jan 17, 2011 at 9:43 PM, Magnus Hagander <magnus(at)hagander(dot)net> wrote:
>> Probably yes, for consistency. I have been thinking for a while,
>> however, that it would be very good if the tools also supported a
>> conninfo string, so you don't have to invent a new option for every new
>> connection option. psql already supports that.
>
> libpq has an option to expand a connection string if it's passed in
> the database name, it seems. The problem is that this is done on the
> dbname parameter - won't work in pg_dump for example, without special
> treatment, since the db name is used in the client there.
If conninfo is specified, you can just append the "dbname=replication"
into it and pass it to libpq as dbname. I don't think that supporting
conninfo is difficult.
Regards,
--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2011-01-17 13:49:56 | Re: pg_basebackup for streaming base backups |
| Previous Message | Fujii Masao | 2011-01-17 13:30:34 | Re: pg_basebackup for streaming base backups |