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

Passing connection string to pg_basebackup

From: Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>
To: Amit Kapila <amit(dot)kapila(at)huawei(dot)com>
Cc: 'Boszormenyi Zoltan' <zb(at)cybertec(dot)at>, 'Hari Babu' <haribabu(dot)kommi(at)huawei(dot)com>, 'Fujii Masao' <masao(dot)fujii(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org, Magnus Hagander <magnus(at)hagander(dot)net>
Subject: Passing connection string to pg_basebackup
Date: 2013-01-18 10:15:53
Message-ID: 50F920D9.1040804@vmware.com (view raw or flat)
Thread:
Lists: pgsql-bugspgsql-hackers
On 18.01.2013 08:50, Amit Kapila wrote:
> I think currently user has no way to specify TCP keepalive settings from
> pg_basebackup, please let me know if there is any such existing way?

I was going to say you can just use "keepalives_idle=30" in the 
connection string. But there's no way to pass a connection string to 
pg_basebackup on the command line! The usual way to pass a connection 
string is to pass it as the database name, and PQconnect will expand it, 
but that doesn't work with pg_basebackup because it hardcodes the 
database name as "replication". D'oh.

You could still use environment variables and a service file to do it, 
but it's certainly more cumbersome. It clearly should be possible to 
pass a full connection string to pg_basebackup, that's an obvious oversight.

- Heikki


In response to

Responses

pgsql-hackers by date

Next:From: Stefan KellerDate: 2013-01-18 11:25:18
Subject: Re: 9.3 Pre-proposal: Range Merge Join
Previous:From: Amit kapilaDate: 2013-01-18 10:05:26
Subject: Re: Proposal for Allow postgresql.conf values to be changed via SQL [review]

pgsql-bugs by date

Next:From: TsunezumiDate: 2013-01-18 11:26:57
Subject: Re: BUG #7814: Rotation of the log is not carried out.
Previous:From: Amit KapilaDate: 2013-01-18 06:50:58
Subject: Re: Review of "pg_basebackup and pg_receivexlog to use non-blocking socket communication", was: Re: Re: [BUGS] BUG #7534: walreceiver takes long time to detect n/w breakdown

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