Re: DIAG [HY000] server closed the connection unexpectedly

Поиск
Список
Период
Сортировка
От Tsunakawa, Takayuki
Тема Re: DIAG [HY000] server closed the connection unexpectedly
Дата
Msg-id 0A3221C70F24FB45833433255569204D1F6349C4@G01JPEXMBYT05
обсуждение исходный текст
Ответ на Re: DIAG [HY000] server closed the connection unexpectedly  ("Jon Raiford" <Raiford@labware.com>)
Ответы Re: DIAG [HY000] server closed the connection unexpectedly  ("Jon Raiford" <Raiford@labware.com>)
Список pgsql-odbc
Hi, Jon, Inoue-san,

Inoue-san,
The attached patch is rebased on HEAD.


Jon,

From: Jon Raiford [mailto:Raiford@labware.com]
> Yes, I can see that the code does answer 08S01, however it is being reported
> as 08001 to the application.  This can be seen even in the ODBC trace.  I'm
> not sure why it is changed.  Maybe this is a symptom of a bigger problem?

Didn't the 08001 get returned after you failed to reconnect?  As follows, I got 08S01 when I killed backend while it
wasrunning an SQL statement (e.g. SELECT pg_sleep(1000)). 

[isql command of unixODBC]
$ isql -v postgres
...
SQL> select pg_sleep(1000);
[ISQL]ERROR: Could not SQLExecute
[08S01]server closed the connection unexpectedly
    This probably means the server terminated abnormally
    before or while processing the request.
;
The connection has been lost
SQL>

[my test app using SQLExecDirect]
08S01: server closed the connection unexpectedly
    This probably means the server terminated abnormally
    before or while processing the request.
;
The connection has been lost

Regards
Takayuki Tsunakawa



Вложения

В списке pgsql-odbc по дате отправления:

Предыдущее
От: "Fred Parkinson"
Дата:
Сообщение: Re: xmin when linked tables are updated?
Следующее
От: "Tsunakawa, Takayuki"
Дата:
Сообщение: [RFC] Changing the default of UseDeclareFetch and Protocol (statement -> transaction rollback)