-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160
Vincent Veyron wrote:
> I suppose you use DBD::Pg, whose current default isolation
> transaction level is ``Serializable''
Just to set the record straight for the archives, DBD::Pg makes
no changes at all to the isolation level. The only way to change
your level when using DBD::Pg would be to issue a SQL command:
$dbh->do('SET TRANSACTION ISOLATION LEVEL SERIALIZABLE');
(The *default* transaction isolation level can be changed in your
postgresql.conf, and it is set to 'read committed' when the
postgresql.conf is created via initdb.)
- --
Greg Sabino Mullane greg@xxxxxxxxxxxx
End Point Corporation http://www.endpoint.com/
PGP Key: 0x14964AC8 201404181453
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-----BEGIN PGP SIGNATURE-----
iEYEAREDAAYFAlNRdVkACgkQvJuQZxSWSsiuRwCg1Xi3r8eS1bdKmkfpRvQiKY2j
yEwAoOwf8aeQqS9xczgKyKkUbgqJq9aV
=rjAZ
-----END PGP SIGNATURE-----
--
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
