[ psqlodbc-Bugs-1010541 ] applications crash with SIGPIPE - Mailing list pgsql-odbc

From
Subject [ psqlodbc-Bugs-1010541 ] applications crash with SIGPIPE
Date
Msg-id 20081230230029.6C12B17ADE50@pgfoundry.org
Whole thread Raw
List pgsql-odbc
Bugs item #1010541, was opened at 2008-12-29 20:42
You can respond by visiting:
http://pgfoundry.org/tracker/?func=detail&atid=538&aid=1010541&group_id=1000125

Category: None
Group: None
Status: Open
Resolution: None
Priority: 3
Submitted By: Brian Feldman (brianfeldman)
>Assigned to: Hiroshi Inoue (hinoue)
Summary: applications crash with SIGPIPE

Initial Comment:
Any time a PostgreSQL server is restarted, applications using the ODBC driver to connect to it will get a SIGPIPE and
oftencrash because of it.  Libraries have no business generating SIGPIPE, so MSG_NOSIGNAL/MSG_NOSIGPIPE/etc. should be
specifiedfor the send(2) calls instead. 

----------------------------------------------------------------------

>Comment By: Hiroshi Inoue (hinoue)
Date: 2008-12-30 23:00

Message:
I can't such values in Windows. Is it related to *nix platforms? If so I would take care od it in the next release.


----------------------------------------------------------------------

You can respond by visiting:
http://pgfoundry.org/tracker/?func=detail&atid=538&aid=1010541&group_id=1000125

pgsql-odbc by date:

Previous
From:
Date:
Subject: [ psqlodbc-Bugs-1002054 ] SQLSetDescField with SQL_DESC_INDICATOR_PTR has no effect.
Next
From:
Date:
Subject: [ psqlodbc-Bugs-1010397 ] SQLForeignKeys no rows returned