Re: Synchronous Log Shipping Replication
От | Tom Lane |
---|---|
Тема | Re: Synchronous Log Shipping Replication |
Дата | |
Msg-id | 28487.1221147665@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: Synchronous Log Shipping Replication (Markus Wanner <markus@bluegap.ch>) |
Ответы |
Re: Synchronous Log Shipping Replication
Re: Synchronous Log Shipping Replication |
Список | pgsql-hackers |
Markus Wanner <markus@bluegap.ch> writes: > Tom Lane wrote: >> Sooner or later we shall have to bite the bullet and set up a >> multiplexing system to transmit multiple event types to backends with >> just one signal. We already did it for signals to the postmaster. > Agreed. However, it's non-trivial if you want reliable queues (i.e. no > message skipped, as with signals) for varying message sizes. No, that's not what I had in mind at all, just the ability to deliver one of a specified set of event notifications --- ie, get around the fact that Unix only gives us two user-definable signal types. For signals sent from other backends, it'd be sufficient to put a bitmask field into PGPROC entries, which the sender could OR bits into before sending the one "real" signal event (either SIGUSR1 or SIGUSR2). I'm not sure what to do if we need signals sent from processes that aren't connected to shared memory; but maybe we need not cross that bridge here. (Also, I gather that the Windows implementation could already support a bunch more signal types without much trouble.) regards, tom lane
В списке pgsql-hackers по дате отправления: