Re: Stats Collector Error 7.4beta1 and 7.4beta2

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Jan Wieck <JanWieck(at)Yahoo(dot)com>
Cc: Kurt Roeckx <Q(at)ping(dot)be>, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, "Matthew T(dot) O'Connor" <matthew(at)zeut(dot)net>, akavan(at)cox(dot)net, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Stats Collector Error 7.4beta1 and 7.4beta2
Date: 2003-09-05 18:59:36
Message-ID: 8536.1062788376@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Jan Wieck <JanWieck(at)Yahoo(dot)com> writes:
> Tom Lane wrote:
>> I was about to say "I give up, let's just take out the comparison".

> Which then get's us back to your concern about assuming that HPUX and
> Linux manpages can be taken as "every platform will" and hope all
> kernels will limit the sender for recv() to the connected address.

Well, I'd not have cared to trust just those couple of manpages, but
if it's in the Single Unix Spec then it's more likely that everyone
follows it. Also, I checked my yellowing first edition of Stevens,
and it says the same thing: "only datagrams from this address will be
received by the socket". So I'm thinking that this behavior has been
passed down from the original Berkeley sockets code.

> Since all involved processes are children of the postmaster, we can add
> some other, random number based security signature into the message
> itself. Noone outside will know what that is, it's really hard to guess
> and can be checked with a few int32 compares, not even a function call
> required.

We could do that if we're feeling paranoid, but I'm now leaning to the
view that it's not worth the trouble.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message markw 2003-09-05 19:15:36 Re: [osdldbt-general] Re: Prelimiary DBT-2 Test results
Previous Message Jan Wieck 2003-09-05 18:50:11 Re: Stats Collector Error 7.4beta1 and 7.4beta2