From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
---|---|
To: | "Ross J(dot) Reedstrom" <reedstrm(at)rice(dot)edu> |
Cc: | Frank Joerdens <frank(at)joerdens(dot)de>, <prlw1(at)cam(dot)ac(dot)uk>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: beta3 Solaris 7 (SPARC) port report |
Date: | 2001-01-26 18:41:54 |
Message-ID: | Pine.LNX.4.30.0101261911080.769-100000@peter.localdomain |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
Ross J. Reedstrom writes:
> Hmm, multiple processors, and lots of IPC: I've got a bad feeling
> about this.
Although I'm not absolutely certain, the systems on which I had this
problem were not multi-processor, they were just plain-old workstations in
a university computer lab. At the time (7.0 beta) I had attributed this
problem to the possibly supicious nature of the /tmp partition, since Marc
didn't have any such problems with his Solaris boxes.
After reading Pete Forman's anecdote I looked around some more and found
this:
http://www.cise.ufl.edu/depot/doc/postfix/HISTORY
19990321
Workaround: from now on, Postfix on Solaris uses stream
pipes instead of UNIX-domain sockets. Despite workarounds,
the latter were causing more trouble than anything else on
all systems combined.
There are also some reports that indicate problems in this direction at
http://www.landfield.com/faqs/usenet/software/inn-faq/part2/.
Conclusion: Don't use it.
--
Peter Eisentraut peter_e(at)gmx(dot)net http://yi.org/peter-e/
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2001-01-26 18:49:43 | Re: Performance: Unix sockets vs. TCP/IP sockets |
Previous Message | Steve Leibel | 2001-01-26 18:29:10 | Re: Connection pooling |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2001-01-26 18:54:40 | Re: Open 7.1 items |
Previous Message | Tom Lane | 2001-01-26 18:30:16 | Re: This script will crash the connection |