From: | jwp(at)pgfoundry(dot)org (James William Pye) |
---|---|
To: | pgsql-committers(at)postgresql(dot)org |
Subject: | python - pq: Add BindingsAndExecutings transaction. |
Date: | 2005-09-12 22:14:05 |
Message-ID: | 20050912221405.0E4451125F68@pgfoundry.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
Log Message:
-----------
Add BindingsAndExecutings transaction. This provides a substantial optimization
for mass insertions. In addition, add the concept of non-fatal exceptions.
Exceptions in a transaction are meant to be fatal to the connection. However,
for BindingsAndExecutings and one other, when the receptor specifies an iterator
to push, it must execute out-of-transaction code that can raise an exception.
These exceptions can be safely caught without a connection fatality, so store it
in 'nf_exc_info' for later use/raising.
Modified Files:
--------------
pq/src:
client3.py (r1.8 -> r1.9)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/python/pq/src/client3.py.diff?r1=1.8&r2=1.9)
From | Date | Subject | |
---|---|---|---|
Next Message | James William Pye | 2005-09-12 22:14:55 | python - pq: Reflect recent changes. |
Previous Message | Neil Conway | 2005-09-12 22:11:39 | pgsql: Make the documentation of GUC variables a separate chapter, |