| From: | Markus Wanner <markus(at)bluegap(dot)ch> |
|---|---|
| To: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
| Cc: | ITAGAKI Takahiro <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Synchronous Log Shipping Replication |
| Date: | 2008-09-11 13:00:08 |
| Message-ID: | 48C91658.2030504@bluegap.ch |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
Fujii Masao wrote:
> Umm... backends have already used SIGUSR1. PostgresMain() sets up a signal
> handler for SIGUSR1 as follows.
Uh.. right. Thanks for pointing that out. Maybe just use SIGPIPE for now?
> Yes, since WAL sender waits on select(), it's convenient to use signal
> for the notification *from backends to WAL sender*, I think too.
..and I'd say you better use the same for WAL sender to backend
communication, just for the sake of simplicity (and thus maintainability).
Regards
Markus Wanner
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Markus Wanner | 2008-09-11 13:07:19 | Re: Synchronous Log Shipping Replication |
| Previous Message | Tom Lane | 2008-09-11 12:54:48 | Re: Synchronous Log Shipping Replication |