Re: pg_recvlogical use of SIGHUP

From: Dave Cramer <davecramer(at)gmail(dot)com>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: pg_recvlogical use of SIGHUP
Date: 2018-07-06 19:15:31
Message-ID: CADK3HH+cKYTLsJ=GVaPuegqm1RivcNw0+dQvSd7TA8-6arSE6Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

>
>
> On 6 July 2018 at 14:11, Andres Freund <andres(at)anarazel(dot)de> wrote:
>
>> Hi,
>>
>> On 2018-07-06 13:49:37 -0400, Dave Cramer wrote:
>> > There is some undocumented (nothing in the docs) code that allows for
>> > closing reopening the output file for pg_recvlogical.
>> >
>> > Since this doesn't change the name of the file in the process I'm
>> wondering
>> > how one might actually use this "feature" ?
>>
>> You can rename the file, then sighup, no? Renaming while the file is
>> open will continue to write into the renamed file, but sighup'ing will
>> use the original name.
>>
>
> That is the missing piece, thanks!
> I'll prepare a patch for the docs
>

See attached patch.

Attachment Content-Type Size
pg_recvlogical.patch application/octet-stream 1.2 KB

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Arthur Zakirov 2018-07-06 19:17:02 Re: PATCH: Update snowball stemmers
Previous Message Robert Haas 2018-07-06 19:14:01 Re: Explain buffers wrong counter with parallel plans