Received: from orion3.ori-ind.com (IDENT:root@[206.81.197.190])
	by hub.org (8.9.3/8.9.3) with ESMTP id SAA22833
	for <pgsql-interfaces@postgreSQL.org>;
	Wed, 8 Sep 1999 18:42:03 -0400 (EDT) (envelope-from ken@ori-ind.com)
Received: from ken (stimpy.ori-ind.com [192.168.61.96])
	by orion3.ori-ind.com (8.8.7/8.8.7) with SMTP id QAA22010;
	Wed, 8 Sep 1999 16:05:06 -0700
Message-Id: <3.0.1.32.19990908153940.00960e20@ori-ind.com>
X-Sender: ken@ori-ind.com
X-Mailer: Windows Eudora Pro Version 3.0.1 (32)
Date: Wed, 08 Sep 1999 15:39:40 -0700
To: Tom Lane <tgl@sss.pgh.pa.us>
From: "Ken J. Wright" <ken@ori-ind.com>
Subject: Re: [INTERFACES] firewall crashes backend 
Cc: pgsql-interfaces@postgreSQL.org
In-Reply-To: <1301.936828585@sss.pgh.pa.us>
References: <Your message of Wed, 08 Sep 1999 13:31:25 -0700
	<3.0.1.32.19990908133125.0095bb50@ori-ind.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"

At 18:09 09/08/1999 -0400, Tom Lane wrote:
>"Ken J. Wright" <ken@ori-ind.com> writes:
>> When connecting to postgresql 6.5.1 through a socks5 firewall via ODBC, the
>> following error occurs:
>
>> ERROR: postmaster: StreamConnection: accept: No route to host
>
>> Then the backend crashes.
>
>I think you mean the postmaster crashes?

Yes I did mean postmaster, however you just gave me absolute definition
between the postmaster & a backend postgres ;-)

>
>> Although the firewall is probably causing the routing trouble, it seems a
>> bit extreme for the backend to crash!
>
>I agree.  This looks like a context problem: the StreamConnection
>routine is calling elog() to report the error --- but elog expects
>to be inside a running backend, not the postmaster process.  Trying
>to send to the client is no good, and trying to longjmp back to the
>backend execution loop is even less good :-(
>
>StreamConnection should probably just use perror to report the error
>on stderr.  There's no hope of telling the client about it...

Tom, this raises a question. I never really know whether reporting these
errors via the interfaces list is adequate to get the fix in a future
snapshot or full release. Should I submit an official bug report, or is
this good enough to enter the pipeline? And how might I get confirmation on
a fix. I don't follow the cvs, but probably there is a change log there?
Even the listed changes/fixes for the full/patch releases are a bit terse
and sometimes difficult to know if the listed fixes have cured a problem.

Ken