Re: [HACKERS] PATCH: Batch/pipelining support for libpq
От | Daniel Verite |
---|---|
Тема | Re: [HACKERS] PATCH: Batch/pipelining support for libpq |
Дата | |
Msg-id | 149fe7fe-eb81-4ff4-a725-efbdda9f6169@manitou-mail.org обсуждение исходный текст |
Ответ на | Re: [HACKERS] PATCH: Batch/pipelining support for libpq (Vaishnavi Prabakaran <vaishnaviprabakaran@gmail.com>) |
Ответы |
Re: [HACKERS] PATCH: Batch/pipelining support for libpq
|
Список | pgsql-hackers |
Hi, I notice that PQsetSingleRowMode() doesn't work when getting batch results. The function is documented as: " int PQsetSingleRowMode(PGconn *conn); This function can only be called immediately after PQsendQuery or one of its sibling functions, before any other operation on the connection such as PQconsumeInput or PQgetResult" But PQbatchQueueProcess() unconditionally clears conn->singleRowMode, so whatever it was when sending the query gets lost, and besides other queries might have been submitted in the meantime. Also if trying to set that mode when fetching like this while (QbatchQueueProcess(conn)) { r = PQsetSingleRowMode(conn); if (r!=1) { fprintf(stderr, "PQsetSingleRowMode() failed"); } .. it might work the first time, but on the next iterations, conn->asyncStatus might be PGASYNC_READY, which is a failure condition for PQsetSingleRowMode(), so that won't do. ISTM that the simplest fix would be that when in batch mode, PQsetSingleRowMode() should register that the last submitted query does request that mode, and when later QbatchQueueProcess dequeues the batch entry for the corresponding query, this flag would be popped off and set as the current mode. Please find attached the suggested fix, against the v5 of the patch. Best regards, -- Daniel Vérité PostgreSQL-powered mailer: http://www.manitou-mail.org Twitter: @DanielVerite -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
Вложения
В списке pgsql-hackers по дате отправления: