Re: Statistics collector port / unix dom. socket?
| От | Scott Marlowe |
|---|---|
| Тема | Re: Statistics collector port / unix dom. socket? |
| Дата | |
| Msg-id | w2ydcc563d11005041304ufc8ee23dy2e0873df298d2b5f@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Statistics collector port / unix dom. socket? (Peter Sabaini <peter.sabaini@ait.ac.at>) |
| Ответы |
Re: Statistics collector port / unix dom. socket?
|
| Список | pgsql-admin |
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.
В списке pgsql-admin по дате отправления: