| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Dave Cramer <davecramer(at)gmail(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: pg_recvlogical use of SIGHUP |
| Date: | 2018-07-06 18:11:48 |
| Message-ID: | 20180706181148.5bh2xi2fp7nb4jf4@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | Postg스포츠 토토 사이트SQL |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Larry Rosenman | 2018-07-06 18:27:33 | "interesting" issue with restore from a pg_dump with a database-wide search_path |
| Previous Message | Dave Cramer | 2018-07-06 17:49:37 | pg_recvlogical use of SIGHUP |