| 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 18:37:33 |
| Message-ID: | CADK3HHKC9hC9oo9qSi1JJHEVML9iHQ+=69H+rar4fsGsOym6UA@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
Dave Cramer
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Larry Rosenman | 2018-07-06 18:37:47 | Re: "interesting" issue with restore from a pg_dump with a database-wide search_path |
| Previous Message | Andres Freund | 2018-07-06 18:37:32 | Re: pgbench issue |