From: | Magnus Hagander <magnus(at)hagander(dot)net> |
---|---|
To: | Thom Brown <thom(at)linux(dot)com> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: pg_receivexlog stops upon server restart |
Date: | 2012-05-24 12:05:14 |
Message-ID: | CABUevEzwfXJ_UsKUVVk0F8QhNoACseQLSORGptV52oP_JB0phg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Apr 19, 2012 at 1:00 PM, Thom Brown <thom(at)linux(dot)com> wrote:
> On 10 April 2012 21:07, Magnus Hagander <magnus(at)hagander(dot)net> wrote:
>> On Friday, April 6, 2012, Thom Brown wrote:
>>>
>>> Hi,
>>>
>>> I've tried out pg_receivexlog and have noticed that when restarting
>>> the cluster, pg_receivexlog gets cut off... it doesn't keep waiting.
>>> This is surprising as the DBA would have to remember to start
>>> pg_receivexlog up again.
>>>
>>
>> This is intentional as far as that's how the code was written, there's not a
>> malfunctioning piece of code somewhere.
>>
>> It would probably make sense to have an auto-reconnect feature, and to have
>> an option to turn it on/off.
>>
>> If you haven't already (my wifi here is currently quite useless, which is
>> why I'm working on my email backlog, so I can't check), please add it to the
>> open items list.
>
> I think it would also be useful to add a paragraph to the
> documentation stating use-cases for this feature, and its advantages.
Attached is a patch that implements this. Seems reasonable?
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
Attachment | Content-Type | Size |
---|---|---|
pg_receivexlog_loop.patch | application/octet-stream | 4.9 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Magnus Hagander | 2012-05-24 12:09:41 | shared_preload_libraries path |
Previous Message | Gurjeet Singh | 2012-05-24 11:51:36 | Creating multiple indexes in one table scan. |