Re: pg_recvlogical use of SIGHUP - Mailing list pgsql-hackers

From Andres Freund
Subject Re: pg_recvlogical use of SIGHUP
Date
Msg-id 20180706181148.5bh2xi2fp7nb4jf4@alap3.anarazel.de
Whole thread Raw
In response to pg_recvlogical use of SIGHUP  (Dave Cramer <davecramer@gmail.com>)
Responses Re: pg_recvlogical use of SIGHUP
List pgsql-hackers
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.

Greetings,

Andres Freund


pgsql-hackers by date:

Previous
From: Dave Cramer
Date:
Subject: pg_recvlogical use of SIGHUP
Next
From: Larry Rosenman
Date:
Subject: "interesting" issue with restore from a pg_dump with a database-widesearch_path