Skip site navigation (1) Skip section navigation (2)

python - pq: Refine extended protocol transactions.

From: jwp(at)pgfoundry(dot)org (James William Pye)
To: pgsql-committers(at)postgresql(dot)org
Subject: python - pq: Refine extended protocol transactions.
Date: 2005-08-11 22:16:21
Message-ID: 20050811221621.D67031125018@pgfoundry.org (view raw or flat)
Thread:
Lists: pgsql-committers
Log Message:
-----------
Refine extended protocol transactions.

The extended protocol messages require that a FlushMessage is sent to
"terminate the operation". With one message per flush, extended protocol
transactions can be quite taxing. To ease this, reorganize the extended query
transactions so that the base single message transactions can be easily
inherited to create compound transactions with a single Flush. Three new
compound transactions appear at the end of client3.

Also, remove the unused rob.notices list from client3.Transaction.

Modified Files:
--------------
    pq/src:
        client3.py (r1.4 -> r1.5)
        (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/python/pq/src/client3.py.diff?r1=1.4&r2=1.5)
    pq/test:
        client3.py (r1.3 -> r1.4)
        (http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/python/pq/test/client3.py.diff?r1=1.3&r2=1.4)

pgsql-committers by date

Next:From: Tom LaneDate: 2005-08-11 22:53:41
Subject: pgsql: EINTR return from connect() should be treated exactly the same as
Previous:From: James William PyeDate: 2005-08-11 22:03:40
Subject: python - pq: Use () instead of tuple(), and make Describe, Close, and

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group