Bruce Momjian <[EMAIL PROTECTED]> wrote:
>
>
> You will be glad to know that 8.0 will use a different implementation
> for thread handling of SIGPIPE, though your asynchronous handling of
> SIGPIPE will still cause problems.
So-noted.
Jim
---(end of broadcast)--
Tom Lane <[EMAIL PROTECTED]> wrote:
>
> [EMAIL PROTECTED] (Jim Seymour) writes:
> > I'm kind of wondering if anybody on the dev team noticed this and
> > what, if anything, they planned to do with it?
>
> Can we make it "#ifdef SOLARIS7" somehow? I'm uneager to put a
> performance penalty on eve
You will be glad to know that 8.0 will use a different implementation
for thread handling of SIGPIPE, though your asynchronous handling of
SIGPIPE will still cause problems.
---
Jim Seymour wrote:
> Hi,
>
> I'm kind of wond
[EMAIL PROTECTED] (Jim Seymour) writes:
> I'm kind of wondering if anybody on the dev team noticed this and
> what, if anything, they planned to do with it?
Can we make it "#ifdef SOLARIS7" somehow? I'm uneager to put a
performance penalty on every platform because of an admittedly
broken signal
Hi,
I'm kind of wondering if anybody on the dev team noticed this and
what, if anything, they planned to do with it?
Jim
[EMAIL PROTECTED] (Jim Seymour) wrote:
>
>
> Hi,
>
> Environment:
>
> SunOS 5.7 Generic_106541-29 sun4u sparc SUNW,UltraSPARC-IIi-Engine
> Postgresql-7.4.6
>
Hi,
Environment:
SunOS 5.7 Generic_106541-29 sun4u sparc SUNW,UltraSPARC-IIi-Engine
Postgresql-7.4.6
Build config: --with-java --enable-thread-safety
gcc version 3.3.1
less-381
readline-4.3
$ echo $PAGER
/usr/local/bin/less
$ echo $LESS
-e
I recently
