| From: | "Adam Rich" <adam(dot)r(at)sbcglobal(dot)net> |
|---|---|
| To: | "'Ivan Sergio Borgonovo'" <mail(at)webthatworks(dot)it>, <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Multiple result sets |
| Date: | 2008-06-01 21:19:16 |
| Message-ID: | 041401c8c42d$2609ad80$721d0880$@r@sbcglobal.net |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
> > 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.
>
Yes, serializable transactions fail if they attempt to modify data
which has changed since the beginning of the transaction. If the
OP's ajax call kicks off 5 queries in a serializable transaction,
there is the potential for failure if two ajax calls initiate
simultaneous serializable transactions modifying data.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | joe | 2008-06-01 22:24:04 | Re: Multiple result sets |
| Previous Message | Clodoaldo | 2008-06-01 21:11:17 | Re: Multiple result sets |