| From: | Ivan Sergio Borgonovo <mail(at)webthatworks(dot)it> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Multiple result sets |
| Date: | 2008-06-01 21:05:12 |
| Message-ID: | 20080601230512.5b16c3d3@dawn.webthatworks.it |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Sun, 1 Jun 2008 15:36:14 -0500
"Adam Rich" <adam(dot)r(at)sbcglobal(dot)net> wrote:
> I am not familiar with the python library, but that looks correct
> to me. You can always test it by adding a sleep between your two
> queries and modifying the database from a console connection
> during the sleep.
> Note that I'm assuming your 5 queries are all read-only selects.
> If you're modifying data during your queries, and another
> concurrent database connection modifies the same data during your
> transaction, the later modifications will fail under serializable
> isolation.
Which one will fail? the second query or the serializable
transaction.
My understanding was that the serializable transaction will fail.
--
Ivan Sergio Borgonovo
http://www.webthatworks.it
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Clodoaldo | 2008-06-01 21:11:17 | Re: Multiple result sets |
| Previous Message | Adam Rich | 2008-06-01 20:36:14 | Re: Multiple result sets |