Re: unite recovery.conf and postgresql.conf - Mailing list pgsql-hackers

From Fujii Masao
Subject Re: unite recovery.conf and postgresql.conf
Date
Msg-id CAHGQGwEPL8u=e0-evf7+FiQnRMwAXg46cHKvOP9YPq4SOT61iA@mail.gmail.com
Whole thread Raw
In response to Re: unite recovery.conf and postgresql.conf  (Fujii Masao <masao.fujii@gmail.com>)
Responses Re: unite recovery.conf and postgresql.conf
List pgsql-hackers
On Tue, Sep 20, 2011 at 3:38 PM, Fujii Masao <masao.fujii@gmail.com> wrote:
>>> What about "recovery.trigger"?
>
> I'm OK with that name.
<snip>
>>> * is there any security hazard from ordinary users being able to see
>>>   what settings had been used?
>>
>> primary_conninfo could be a problem, since it's possible to set a password there.
>
> True. I agree that primary_conninfo should be restricted to superuser.

Though there is still ongonig discussion, since there is no objection about
the above two changes, I revised the patch that way. And I fixed the minor
bug handling the default value of recovery_target_timeline wrongly.
Attached is the revised version of the patch.

Regards,

--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center

Attachment

pgsql-hackers by date:

Previous
From: Kohei KaiGai
Date:
Subject: Re: contrib/sepgsql regression tests are a no-go
Next
From: andurkar
Date:
Subject: Postgresql parser