Re: Synch Rep: communication between backends and walsender - Mailing list pgsql-hackers

From Markus Wanner
Subject Re: Synch Rep: communication between backends and walsender
Date
Msg-id 4A3CA659.7080204@bluegap.ch
Whole thread Raw
In response to Synch Rep: communication between backends and walsender  (Fujii Masao <masao.fujii@gmail.com>)
Responses Re: Synch Rep: communication between backends and walsender  (Fujii Masao <masao.fujii@gmail.com>)
List pgsql-hackers
Hi,

Fujii Masao wrote:
> One of the major complaints about the current synch rep patch is that
> signals are used for communication between backends and walsender.
> On some platforms, a signal doesn't interrupt sleep (i.e. poll or select
> system call), which would increase the performance overhead of
> replication.

Reading the past messages on this topic, I realized that this problem so
far only affects HPUX. I fear the proposed UDP/semaphores approach might
have a similar gotcha on at least one of the supported platforms, too.
Limits of open file descriptors come to mind, for example. Or kernel
packet filtering rules, as mentioned in pgstat.c.

If I understand correctly, even Postgres itself suffers from that
problem on HPUX (even though the consequences aren't dramatic, as
pointed out by Tom). Plus we are not completely save from syscalls
returning EINTR due to SA_RESTART not being set for SIGALRM.

So, does it really make sense to take care of this issue as part of the
sync rep patch?

Regards

Markus Wanner


pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: 8.4 open item: copy performance regression?
Next
From: Greg Stark
Date:
Subject: Re: 8.4 open item: copy performance regression?