Re: [snafu] isolation-level change in 2.4.2 - Mailing list psycopg

From Federico Di Gregorio
Subject Re: [snafu] isolation-level change in 2.4.2
Date
Msg-id 4EE9EF8E.6070206@dndg.it
Whole thread Raw
In response to Re: [snafu] isolation-level change in 2.4.2  (Daniele Varrazzo <daniele.varrazzo@gmail.com>)
Responses Re: [snafu] isolation-level change in 2.4.2  (Daniele Varrazzo <daniele.varrazzo@gmail.com>)
List psycopg
On 15/12/11 13:55, Daniele Varrazzo wrote:
> First note: even if currently postgres behaviour is the same at levels
> read committed and read uncommitted, they are still two distinct
> levels:
>
>      test=>  set default_transaction_isolation = 'read uncommitted';
>      SET
>      test=>  SHOW default_transaction_isolation;
>       default_transaction_isolation
>      -------------------------------
>       read uncommitted
>      (1 row)
>
> I think psycopg shouldn't assume the two being equivalent, otherwise
> in the event they will become different in future postgres versions we
> would have older psycopg version not supporting them. Doing it now
> doesn't cost anything.
>
> I've also just noted that the check for pg version not supporting
> levels UNC/REPREAD is in two different points (unfortunately
> set_session and set_isolation_level have no common code path).
>
> I've made a patch against these points, but I'll be able to run the
> complete test grid only this evening.

Merged.

federico


psycopg by date:

Previous
From: Daniele Varrazzo
Date:
Subject: Re: [snafu] isolation-level change in 2.4.2
Next
From: Ronan Dunklau
Date:
Subject: Generic casters for composite types