Received: from sss.sss.pgh.pa.us (sss.pgh.pa.us [209.114.166.2])
	by hub.org (8.9.3/8.9.3) with ESMTP id SAA17931
	for <pgsql-interfaces@postgreSQL.org>;
	Wed, 8 Sep 1999 18:10:51 -0400 (EDT)
	(envelope-from tgl@sss.pgh.pa.us)
Received: from sss.sss.pgh.pa.us (localhost [127.0.0.1])
	by sss.sss.pgh.pa.us (8.9.1/8.9.1) with ESMTP id SAA01303;
	Wed, 8 Sep 1999 18:09:45 -0400 (EDT)
To: "Ken J. Wright" <ken@ori-ind.com>
cc: pgsql-interfaces@postgreSQL.org
Subject: Re: [INTERFACES] firewall crashes backend 
In-reply-to: Your message of Wed, 08 Sep 1999 13:31:25 -0700
	<3.0.1.32.19990908133125.0095bb50@ori-ind.com>
Date: Wed, 08 Sep 1999 18:09:45 -0400
Message-ID: <1301.936828585@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>

"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?

> 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...

			regards, tom lane