pgpool: Revert "Fix do_query to send sync rather than flush."

From: Tatsuo Ishii <ishii(at)postgresql(dot)org>
To: pgpool-committers(at)lists(dot)postgresql(dot)org
Subject: pgpool: Revert "Fix do_query to send sync rather than flush."
Date: 2026-09-06 22:56:56
Message-ID: E1x3LnC-00000000yHk-3sHW@gothos.postgresql.org
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgpool-committers

Revert "Fix do_query to send sync rather than flush."

This reverts commit e4a3a0c13e4b5e1a015aca3db238b21b88e73e2f.

This breaks implicit transaction behavior created by a pipeline.
-----------------------------------------------------------------
$ psql -p 11000 -a -f failure.sql test
DROP TABLE test;
DROP TABLE
-- start a pipeline
\startpipeline
-- CREATE a table
CREATE TABLE test(i int);
-- SELECT non-existent table, which raises an error,
-- and aborts the implicit transaction started by the pipeline.
SELECT * from a;
-- Recover from the error and closes the implicit transaction.
\syncpipeline
\endpipeline
CREATE TABLE
psql:failure.sql:11: ERROR: relation "a" does not exist
LINE 1: SELECT * from a;
^
-- Try to SELECT the table created in the previous pipeline.
-- This should fail because the creation of the table "test" was rollbacked.
SELECT * from test;
i
---
(0 rows)
-----------------------------------------------------------------

In this example, a table named "test" is created in a pipeline. Then
a SELECT is executed. Because the SELECT tries to retrieve rows from
non-existent table "a", it causes an error and a roll back of the
implicit transaction started by the pipeline. As a result, the table
"test" created in the pipeline does not exist at the end of the
pipeline. However, a "sync" message was issued by do_query() while
obtaining information regarding table "a". As the sync message caused
commit of the implicit transaction started by the pipeline, creation
of "test" was not roll backed by the subsequent erroneous SELECT.

IMO this is a serious data consistency issue because it breaks the
transaction semantics. If I directly connects to PostgreSQL or pgpool
by the previous commit, and run the script, it ends up with:

SELECT * from test;
psql:failure.sql:14: ERROR: relation "test" does not exist
LINE 1: SELECT * from test;
^
which is the expected behavior.

Discussion: https://www.postgresql.org/message-id/20260907.062521.1780975513572548706.ishii@postgresql.org
Backpatch-through: v4.3

Branch
------
master

Details
-------
https://git.postgresql.org/gitweb?p=pgpool2.git;a=commitdiff;h=6f66cdbf0cc043bdd0f9fe7484fb1de8a99bbea3

Modified Files
--------------
src/protocol/pool_process_query.c | 26 +++++++++++++---------
.../tests/039.log_backend_messages/expected.s | 1 +
2 files changed, 17 insertions(+), 10 deletions(-)

Browse pgpool-committers by date

  From Date Subject
Next Message Ernesto Montilva 2026-09-07 14:59:56 50-60ms per-query overhead in PgPool-II 4.7 vs direct connection
Previous Message Tatsuo Ishii 2026-09-06 22:56:51 pgpool: Revert "Fix do_query to send sync rather than flush."