From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Ken J(dot) Wright" <ken(at)ori-ind(dot)com> |
Cc: | pgsql-interfaces(at)postgreSQL(dot)org |
Subject: | Re: [INTERFACES] firewall crashes backend |
Date: | 1999-09-08 22:09:45 |
Message-ID: | 1301.936828585@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-interfaces |
"Ken J. Wright" <ken(at)ori-ind(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 1999-09-08 22:14:31 | Re: [INTERFACES] Internal errors when creating views ... |
Previous Message | Ken J. Wright | 1999-09-08 20:31:25 | firewall crashes backend |