Re: pg_recvlogical use of SIGHUP

2018-07-06 Thread Dave Cramer
> > > On 6 July 2018 at 14:11, Andres Freund 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

Re: pg_recvlogical use of SIGHUP

2018-07-06 Thread Dave Cramer
On 6 July 2018 at 14:11, Andres Freund 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

Re: pg_recvlogical use of SIGHUP

2018-07-06 Thread Andres Freund
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

pg_recvlogical use of SIGHUP

2018-07-06 Thread Dave Cramer
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" ? I could see it being useful if we were to be able to