Re: Stats Collector Error 7.4beta1 and 7.4beta2

From: Bruno Wolff III <bruno(at)wolff(dot)to>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl>, Andrew Dunstan <andrew(at)dunslane(dot)net>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Stats Collector Error 7.4beta1 and 7.4beta2
Date: 2003-09-10 18:42:18
Message-ID: 20030910184218.GA29202@wolff.to
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Sep 10, 2003 at 12:49:31 -0400,
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> The question is whether any of this is worth worrying about in PG.
> ISTM the correct solution to such a risk is to tighten your kernel's
> packet filtering, not harden one piece of one application.

On linux at least, it is pretty easy to make sure packets claiming to
be from loopback are dropped if they don't come in on the loopback
interface.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Greg Stark 2003-09-10 18:46:05 quirk of array type processing
Previous Message Jon Jensen 2003-09-10 18:36:39 Re: massive quotes?