public inbox for [email protected]
help / color / mirror / Atom feedFrom: =?gb18030?B?TGlDaG9uZw==?= <[email protected]>
To: =?gb18030?B?RGF2ZSBDcmFtZXI=?= <[email protected]>
Cc: =?gb18030?B?cGdzcWwtb2RiY0Bwb3N0Z3Jlc3FsLm9yZw==?= <[email protected]>
Subject: =?gb18030?B?u9i4tKO6IGR1cmluZyBjYWxsIFNRTEZyZWVIYW5k?= =?gb18030?B?bGUsIHRoZSBjb25uZWN0aW9uIGlzIGJyb2tlbi4g?= =?gb18030?B?Y2xpZW50IGNhbid0IGJlIG5vdGlmaWVkLg==?=
Date: Wed, 6 Dec 2023 10:30:07 +0800
Message-ID: <[email protected]> (raw)
Hi,Dave Cramer
not master, it's base on psqlodbc-13.02.0000.
LiChong
[email protected]
------------------ 原始邮件 ------------------
发件人: "Dave Cramer" <[email protected]>;
发送时间: 2023年12月6日(星期三) 凌晨5:17
收件人: "LiChong"<[email protected]>;
抄送: "[email protected]"<[email protected]>;
主题: Re: during call SQLFreeHandle, the connection is broken. client can't be notified.
Hi LiChong,
Attached is a patch which is the diff between your file and the current master
There are some differences at the bottom of the file that seem to indicate that your version of the source is older than the current master. Can you confirm?
Also can you send back your changes in a patch file.
I used git diff to produce the attached patch
Dave Cramerwww.postgres.rocks
On Tue, 5 Dec 2023 at 10:05, LiChong <[email protected]> wrote:
你好
事务场景下，SQLFreeHandle调用进行中，连接断开，但是SQLFreeHandle返回SQL_SUCCESS。由于SQLFreeHandle调用连接断开，触发cc_on_abort，将事务取消，在客户端执行commit时，没有与服务端交互并且返回成功，导致客户端以为数据已提交，导致丢数据。
In a transaction scenario, the connection is disconnected while the SQLFreeHandle call is in progress, but SQLFreeHandle returns SQL_SUCCESS. Because the connection is disconnected by the SQLFreeHandle call, the cc_on_abort is triggered, the transaction is canceled, and the client performs a commit without interacting with the server and returning success, causing the client to think that the data has been submitted, resulting in data loss.
call step:
SQLAllocHandle1
sql1
SQLFreeHandle1
SQLAllocHandle2
sql2
SQLFreeHandle2
commit
during call SQLFreeHandle2， the connection is broken. client can't be notified.
we modify the code, in statement.c SC_Destructor and PGAPI_FreeStmt, Is there any other better solution to this problem? Please share your thoughts and suggestions, thanks.
below is psqlodbc log, debug=2
--------------
[7f5843a3a700] bind.c[PDATA_free_params]689: leaving
[7f5843a3a700] results.c[PGAPI_MoreResults]2035: leaving 100
[7f5843a3a700]odbcapi30.[SQLFreeHandle]250: Entering
[7f5843a3a700]statement.[PGAPI_FreeStmt]248: entering...hstmt=0x7f583c044600, fOption=1
[7f5843a3a700] qresult.c[QR_Destructor]344: entering
[7f5843a3a700]statement.[SC_init_Result]536: leaving(0x7f583c044600)
[7f5843a3a700]statement.[SC_Destructor]483: entering self=0x7f583c044600, self->result=(nil), self->hdbc=0xe27cc0
[7f5843a3a700]connection[CC_send_query_append]1809: conn=0xe27cc0, query='DEALLOCATE "_PLAN0x7f583c044600"'
[7f5843a3a700]connection[CC_send_query_append]1891: query_len=32
[7f5843a3a700]connection[CC_send_query_append]1935: [QLOG]PQsendQuery: 0xdf4990 'SAVEPOINT _per_query_svp_;DEALLOCATE "_PLAN0x7f583c044600";RELEASE _per_query_svp_'
[7f5843a3a700] qresult.c[QR_Constructor]173: entering
[7f5843a3a700] qresult.c[QR_Constructor]242: leaving 0x7f583c030380
[7f5843a3a700]connection[handle_pgres_error]864: PG_DIAG_SEVERITY_NONLOCALIZED=(null)
[7f5843a3a700]connection[handle_pgres_error]883: [QLOG] ((null)) (null) '(null)'
[7f5843a3a700]connection[handle_pgres_error]950: error message=server closed the connection unexpectedly
This probably means the server terminated abnormally
before or while processing the request.
(137)
[7f5843a3a700]connection[CC_on_abort]1582: entering opt=2
[7f5843a3a700]connection[CC_on_abort]1604: [QLOG]PQfinish: 0xdf4990
[7f5843a3a700] qresult.c[QR_Destructor]344: entering
[7f5843a3a700] qresult.c[QR_close_result]255: entering
[7f5843a3a700] qresult.c[QR_free_memory]479: entering fcount=0
[7f5843a3a700] qresult.c[QR_free_memory]577: leaving
[7f5843a3a700] qresult.c[QR_close_result]319: leaving
[7f5843a3a700] qresult.c[QR_Destructor]348: leaving
[7f5843a3a700] bind.c[APD_free_params]643: entering self=0x7f583c0447e0
[7f5843a3a700] bind.c[APD_free_params]655: leaving
[7f5843a3a700] bind.c[IPD_free_params]698: entering self=0x7f583c044850
[7f5843a3a700] bind.c[IPD_free_params]709: leaving
[7f5843a3a700] bind.c[PDATA_free_params]663: entering self=0x7f583c044948
[7f5843a3a700] bind.c[PDATA_free_params]689: leaving
[7f5843a3a700]statement.[SC_Destructor]526: leaving
[7f5843a3a700]odbcapi30.[SQLEndTran]171: Entering
[7f5843a3a700] execute.c[PGAPI_Transact]1208: entering hdbc=0xe27cc0, henv=(nil)
[7f5843a3a700]odbcapi30.[SQLAllocHandle]40: Entering
[7f5843a3a700]statement.[PGAPI_AllocStmt]189: entering...
Best Wishes
LiChong
[email protected]
Attachments:
[application/octet-stream] statement.c.patch (1.3K, 3-statement.c.patch)
download | inline diff:
statement.c | 17 ++++++++++++++---
1 file changed, 14 insertions(+), 3 deletions(-)
diff --git a/statement.c b/statement.c
index e7f816f..4867eda 100644
--- a/statement.c
+++ b/statement.c
@@ -296,7 +296,10 @@ PGAPI_FreeStmt(HSTMT hstmt,
if (stmt->execute_parent)
stmt->execute_parent->execute_delegate = NULL;
/* Destroy the statement and free any results, cursors, etc. */
- SC_Destructor(stmt);
+ //SC_Destructor(stmt);
+ /*if the connection was give up,return SQL_ERROR.*/
+ if(SC_Destructor(stmt) == FALSE)
+ return SQL_ERROR;
}
else if (fOption == SQL_UNBIND)
SC_unbind_cols(stmt);
@@ -477,6 +480,7 @@ SC_Constructor(ConnectionClass *conn)
char
SC_Destructor(StatementClass *self)
{
+ char cRet = TRUE;
CSTR func = "SC_Destructor";
QResultClass *res = SC_get_Result(self);
@@ -498,6 +502,13 @@ SC_Destructor(StatementClass *self)
SC_initialize_stmts(self, TRUE);
+
+ if(self->hdbc && !self->hdbc->pqconn)
+ {
+ SC_set_error(self, STMT_COMMUNICATION_ERROR, "connection error.", func);
+ cRet = FALSE;
+ }
+
/* Free the parsed table information */
SC_initialize_cols_info(self, FALSE, TRUE);
@@ -524,8 +535,8 @@ SC_Destructor(StatementClass *self)
free(self);
MYLOG(0, "leaving\n");
-
- return TRUE;
+
+ return cRet;
}
void
reply
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: [email protected]
Cc: [email protected], [email protected]
Subject: Re: =?gb18030?B?u9i4tKO6IGR1cmluZyBjYWxsIFNRTEZyZWVIYW5k?= =?gb18030?B?bGUsIHRoZSBjb25uZWN0aW9uIGlzIGJyb2tlbi4g?= =?gb18030?B?Y2xpZW50IGNhbid0IGJlIG5vdGlmaWVkLg==?=
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox