From: Scott Marlowe <scott.marlowe@gmail.com>
To: Peter Sabaini <peter.sabaini@ait.ac.at>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-admin@postgresql.org
Subject: Re: Statistics collector port / unix dom. socket?
Date: Tue, 4 May 2010 14:04:38 -0600
Message-ID: <w2ydcc563d11005041304ufc8ee23dy2e0873df298d2b5f@mail.gmail.com> (raw)
In-Reply-To: <1273002081.2590.7.camel@w-ehs-psa.telbiomed.at>
References: <1272977816.21378.13.camel@w-ehs-psa.telbiomed.at>
<13335.1272987580@sss.pgh.pa.us>
<1273002081.2590.7.camel@w-ehs-psa.telbiomed.at>
On Tue, May 4, 2010 at 1:41 PM, Peter Sabaini <peter.sabaini@ait.ac.at> wrote:
> 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.
Maybe running them in individual VMs would do that.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: scott.marlowe@gmail.com, peter.sabaini@ait.ac.at, tgl@sss.pgh.pa.us
Subject: Re: Statistics collector port / unix dom. socket?
In-Reply-To: <w2ydcc563d11005041304ufc8ee23dy2e0873df298d2b5f@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox