From: Tom Lane <tgl@sss.pgh.pa.us>
To: Ken J. Wright <ken@ori-ind.com>
Cc: pgsql-interfaces@postgreSQL.org
Subject: Re: [INTERFACES] firewall crashes backend
Date: Wed, 08 Sep 1999 18:09:45 -0400
Message-ID: <1301.936828585@sss.pgh.pa.us> (raw)
In-Reply-To: <3.0.1.32.19990908133125.0095bb50@ori-ind.com>
"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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: tgl@sss.pgh.pa.us, ken@ori-ind.com
Subject: Re: [INTERFACES] firewall crashes backend
In-Reply-To: <1301.936828585@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox