Hello.
I have found an interesting FRONTEND/BACKEND protocol behaviour. Let's
consider following query:
"SELECT 1; SELECT 2; SELECT3; SELECT4;"
1) If I send it as a simple query - I'm getting:
- correct results for SELECT 1; SELECT 2; SELECT3; SELECT4;
- and then one ReadyForQuery response
from backend.
[send_simple.log & recv_simple.log]
2) If I send it as 'PREPARE "SQL_CUR1" AS SELECT 1; SELECT 2; SELECT3;
SELECT4;' and then 'EXECUTE "SQL_CUR1" - I'm getting:
- results for SELECT 1; SELECT2; SELECT 3;
- ReadyForQuery response
- results for SELECT 4;
- one more ReadyForQuery response
from backend
[send_prepared.log & recv_prepared.log]
Is this behavour is correct and expected?
P.s. Tested on Windows with PostgreSQL 8.0, 8.1 and 8.2 with the same
results.
Thank You,
Andrei.
R #þTèR S client_encoding SQL_ASCII S DateStyle ISO,
MDY S integer_datetimes off S is_superuser on S server_encoding SQL_ASCII S server_version 8.2.5 S !session_authorization andrei S $standard_conforming_strings off S TimeZone Europe/Helsinki K
X`M¹Z IS client_encoding UNICODE C SET Z IT
version ÿÿÿÿÿÿ D b XPostgreSQL 8.2.5 on i686-pc-mingw32,
compiled by GCC gcc.exe (GCC) 3.4.2 (mingw-special)C SELECT Z IC
PREPARE T ! ?column? ÿÿÿÿ D 2C SELECT T ! ?column? ÿÿÿÿ D 3C SELECT T ! ?column? ÿÿÿÿ D 4C SELECT Z IT ! ?column? ÿÿÿÿ D 1C SELECT Z I
R Ô²oÍR S client_encoding SQL_ASCII S DateStyle ISO,
MDY S integer_datetimes off S is_superuser on S server_encoding SQL_ASCII S server_version 8.2.5 S !session_authorization andrei S $standard_conforming_strings off S TimeZone Europe/Helsinki K
h]l»Z IS client_encoding UNICODE C SET Z IT
version ÿÿÿÿÿÿ D b XPostgreSQL 8.2.5 on i686-pc-mingw32,
compiled by GCC gcc.exe (GCC) 3.4.2
(mingw-special)C SELECT Z IT ! ?column? ÿÿÿÿ D 1C SELECT T ! ?column? ÿÿÿÿ D 2C SELECT T ! ?column? ÿÿÿÿ D 3C SELECT T ! ?column? ÿÿÿÿ D 4C SELECT Z I
# user andrei database test p (md5******************************** Q %SET
client_encoding to 'UNICODE' Q SELECT version() Q =PREPARE"SQL_CUR1"AS
SELECT 1;SELECT 2;SELECT 3;SELECT 4; Q EXECUTE"SQL_CUR1"
# user andrei database test p (md5******************************** Q %SET
client_encoding to 'UNICODE' Q SELECT version() Q )SELECT 1;SELECT
2;SELECT 3;SELECT 4;
---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster
