From: | "Greg Sabino Mullane" <greg(at)turnstep(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Re: any way for a transaction to "see" inserts done earlier in the transaction? |
Date: | 2014-04-18 18:57:01 |
Message-ID: | ecbbcfb70d57845ae003c161eb9b39ec@biglumber.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
-----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(at)turnstep(dot)com
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-----
From | Date | Subject | |
---|---|---|---|
Next Message | Andy Colson | 2014-04-18 20:24:15 | Re: Could use some advice on search architecture |
Previous Message | Edson Richter | 2014-04-18 18:00:20 | Re: Arduino SQL Connector |