Skip site navigation (1) Skip section navigation (2)

Re: Synchronous Log Shipping Replication

From: Markus Wanner <markus(at)bluegap(dot)ch>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, 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 16:31:46
Message-ID: 48C947F2.4020001@bluegap.ch (view raw or flat)
Thread:
Lists: pgsql-hackers
Hi,

Tom Lane wrote:
> 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.

Ah, okay. And I already thought you'd like imessages :-(

> 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).

That might work for expanding the number of available signals, yes.

Regards

Markus Wanner

In response to

pgsql-hackers by date

Next:From: Tom LaneDate: 2008-09-11 16:43:00
Subject: Re: Potential Join Performance Issue
Previous:From: Lawrence, RamonDate: 2008-09-11 15:52:44
Subject: Re: Potential Join Performance Issue

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group