| From: | Andres Freund <andres(at)2ndquadrant(dot)com> |
|---|---|
| To: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org> |
| Subject: | Re: pg_recvlogical, stdout and SIGHUP |
| Date: | 2014-05-13 13:35:51 |
| Message-ID: | 20140513133551.GC9535@awork2.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2014-05-13 16:31:25 +0300, Heikki Linnakangas wrote:
> pg_recvlogical re-opens the output file on SIGHUP. If the output goes to
> stdout, it will close stdout on SIGHUP. That's a bug, isn't it?
Yes. An annoying one at that because it'll mean a a new connection will
use that fd and we'll start writing stdout stuff to it...
> Another thing I noticed is that if when the output goes to a file, the file
> isn't re-opened immediately on SIGHUP. Only after receiving some data from
> the server. I believe that's also not intentional.
Hm. I can't really get excited about that one. Not doing that seems to
complicate matters unneccessarily. What's the problem here?
Greetings,
Andres Freund
--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2014-05-13 13:53:39 | Re: New timezones used in regression tests |
| Previous Message | Heikki Linnakangas | 2014-05-13 13:31:25 | pg_recvlogical, stdout and SIGHUP |