From: | Raghavendra <raghavendra(dot)rao(at)enterprisedb(dot)com> |
---|---|
To: | Hari Babu <haribabu(dot)kommi(at)huawei(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: pg_basebackup -R option in PG 9.3 beta |
Date: | 2013-05-15 11:10:33 |
Message-ID: | CA+h6AhhWz+=fVYQMfr7FDW04UH01oM-hdXzku5hb29iMTRG4iw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Wed, May 15, 2013 at 4:26 PM, Hari Babu <haribabu(dot)kommi(at)huawei(dot)com>wrote:
> >on Wednesday, May 15, 2013 4:04 PM Raghavendra wrote:****
>
> >In earlier version of primary connection information was enclosed within
> one single quote:****
>
> >primary_conninfo = 'user=postgres host=localhost port=5432'****
>
> >** **
>
> >But, the file created with -R option (recovery.conf) has doubled the
> single quotes for all variable values
> user/host/port/sslmode/sslcompression in primary connection. ****
>
> >** **
>
> >standby_mode = 'on'****
>
> >primary_conninfo = 'user=''postgres'' host=''localhost'' port=''5555''
> sslmode=''disable'' sslcompression=''1'' ' ****
>
> >** **
>
> >Was it intentional to double the singe quotes of variable values ? ****
>
> ** **
>
> Yes, It was intentional to support some of the special characters in
> configuration parameters which can be used in the primary_conninfo.****
>
> ** **
>
> There is a patch in the next commit-fest which is further extending the
> special characters in password.****
>
> Please refer the following link.****
>
> ** **
>
> https://commitfest.postgresql.org/action/patch_view?id=1085****
>
> ** **
>
> Regards,****
>
> Hari babu.****
>
> ** **
>
Thank you.
--Raghav
From | Date | Subject | |
---|---|---|---|
Next Message | Kevin Grittner | 2013-05-15 12:13:19 | Re: Large amount of serialization errors in transactions |
Previous Message | Hari Babu | 2013-05-15 10:56:50 | Re: pg_basebackup -R option in PG 9.3 beta |