On 05/04/2010 02:24 PM, Tom Lane wrote:
We might be able to learn something if you strace the postmaster
while it's trying to start up with "localhost" as the setting.
There will be a lot of output, so send it to a file. Look for
the bind() calls --- on my Linux box the relevant part of the
tra
Peter Sabaini writes:
> On Tue, 2010-05-04 at 11:39 -0400, Tom Lane wrote:
>> I'd suggest backing off your ideas about how much filtering is
>> appropriate for local connections.
> Since we're running multiple database instances with different projects
> on one machine I'd like to isolate them as
On Tue, May 4, 2010 at 1:41 PM, Peter Sabaini wrote:
> On Tue, 2010-05-04 at 11:39 -0400, Tom Lane wrote:
>> Peter Sabaini writes:
>> > it seems Postgres tries to send a UDP packet to a random high port to
>> > communicate with the statistics collector daemon. We have rather strict
>> > packet fi
On Tue, 2010-05-04 at 11:39 -0400, Tom Lane wrote:
> Peter Sabaini writes:
> > it seems Postgres tries to send a UDP packet to a random high port to
> > communicate with the statistics collector daemon. We have rather strict
> > packet filter rules in place, and I'd like to make the system use a
>
If you're using Tomcat or some other Java container that does connection
management restart it and the lock should go away.
Bob Lunney
--- On Fri, 4/30/10, Kamcheung Sham wrote:
> From: Kamcheung Sham
> Subject: [ADMIN] Runaway Locks
> To: [email protected]
> Date: Friday, April 30,
Peter Sabaini writes:
> it seems Postgres tries to send a UDP packet to a random high port to
> communicate with the statistics collector daemon. We have rather strict
> packet filter rules in place, and I'd like to make the system use a
> fixed port for this, or even better a Unix domain socket.
"Daniel J. Summers" writes:
> On 05/03/2010 02:20 PM, Tom Lane wrote:
>> OK, what about 127.0.0.1? Given that "dig localhost" returns that,
>> it *should* behave the same, but obviously something here is not
>> behaving as expected. Also, after you start it with '*', does
>> "psql -h localhost"
Hello,
it seems Postgres tries to send a UDP packet to a random high port to
communicate with the statistics collector daemon. We have rather strict
packet filter rules in place, and I'd like to make the system use a
fixed port for this, or even better a Unix domain socket. Is this
possible (sett
