Hi,
On Tue, Jun 23, 2009 at 1:55 AM, Markus Wannermar...@bluegap.ch wrote:
On the other hand, I think that a semaphore should be used instead of a
signal
at least for backends to wait for walsender. This would turn around
the situation
on HPUX in some degree. In this case, the remaining
Hi,
On Sat, Jun 20, 2009 at 6:05 PM, Markus Wannermar...@bluegap.ch wrote:
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.
Hi,
Fujii Masao wrote:
The perfect solution seems to be to remove SA_RESTART and handle EINTR
in an appropriate way after every syscalls. But, this is very tough job and
has
much influence on whole source code, so I don't think that this should be done
as part of synch rep.
Especially note
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
http://archives.postgresql.org/pgsql-hackers/2008-12/msg00448.php
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
On Tue, Jun 16, 2009 at 12:50 PM, Fujii Masaomasao.fu...@gmail.com wrote:
On some platforms, a signal doesn't interrupt sleep (i.e. poll or select
system call)
say what?
--
Gregory Stark
http://mit.edu/~gsstark/resume.pdf
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
Greg Stark st...@enterprisedb.com writes:
On Tue, Jun 16, 2009 at 12:50 PM, Fujii Masaomasao.fu...@gmail.com wrote:
On some platforms, a signal doesn't interrupt sleep (i.e. poll or select
system call)
say what?
Yup, what he said.
regards, tom lane
--
Sent via
