Re: Statistics collector port / unix dom. socket? - Mailing list pgsql-admin

From Peter Sabaini
Subject Re: Statistics collector port / unix dom. socket?
Date
Msg-id 1273002081.2590.7.camel@w-ehs-psa.telbiomed.at
Whole thread Raw
In response to Re: Statistics collector port / unix dom. socket?  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Statistics collector port / unix dom. socket?  (Scott Marlowe <scott.marlowe@gmail.com>)
Re: Statistics collector port / unix dom. socket?  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-admin
On Tue, 2010-05-04 at 11:39 -0400, Tom Lane wrote:
> Peter Sabaini <peter.sabaini@ait.ac.at> 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. Is this
> > possible (setting a compile time or run time parameter)?
>
> No, the stats collector just uses whatever port bind() chooses for it.

A pity.

> 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 best I can.

Thanks anyway...

peter.

>
>             regards, tom lane



pgsql-admin by date:

Previous
From: Bob Lunney
Date:
Subject: Re: Runaway Locks
Next
From: Scott Marlowe
Date:
Subject: Re: Statistics collector port / unix dom. socket?