From: Ken J. Wright <ken@ori-ind.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-interfaces@postgreSQL.org
Subject: Re: [INTERFACES] firewall crashes backend
Date: Wed, 08 Sep 1999 15:39:40 -0700
Message-ID: <3.0.1.32.19990908153940.00960e20@ori-ind.com> (raw)
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>
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
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: ken@ori-ind.com, tgl@sss.pgh.pa.us
Subject: Re: [INTERFACES] firewall crashes backend
In-Reply-To: <3.0.1.32.19990908153940.00960e20@ori-ind.com>
* 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