[Libpqxx-general] REPEATABLE_READ transaction isolation support?

[Pawel Salek]

Hello everybody,

Since postgresql-9.1, ISO's REPEATABLE READ and SERIALIZABLE
transaction isolation levels are not identical, as described on
http://www.postgresql.org/docs/9.1/static/transaction-iso.html

I think it would make sense to expose this functionality via pqxx.
There are cases when READ_COMMITTED is insufficient and SERIALIZABLE
causes transaction failures with a negative performance impact (seen
it). Some other people report performance loss:
http://postgresql.1045698.n5.nabble.com/Overhead-cost-of-Serializable-Snapshot-Isolation-td4889344.html

Attached patch adds repeatable_read isolation trait. Can it get merged,
please? One might want to add support for read_uncommitted while we are
at it, but maybe it would be premature?

Best regards,

Pawel Salek

[Pawel Salek]

Post by Pawel Salek
Attached patch adds repeatable_read isolation trait.

I can't see any attachment, did it get stripped?

I did attach the patch, I see it in my sentbox :). Anyway, I attached
it also to the Trac ticket:
<http://pqxx.org/development/libpqxx/ticket/259>, too. I was bit sloppy
there and created duplicate ticket 258 - it can be closed.

Pawel

[Pawel Salek]

Can the committers give this ticket 259 a thought, please? What is your
opinion? Is it any problem with having access to REPEATABLE_READ via
libpqxx?

Pawel

Post by Pawel Salek

Post by Pawel Salek
Attached patch adds repeatable_read isolation trait.

I can't see any attachment, did it get stripped?

I did attach the patch, I see it in my sentbox :). Anyway, I attached
<http://pqxx.org/development/libpqxx/ticket/259>, too. I was bit
sloppy there and created duplicate ticket 258 - it can be closed.
Pawel