On 11/07/11 3:30 PM, Edson Richter wrote:
Thanks for the fast answer. Is there any way to avoid that? I mean, in MS SQL Server, I do have "with no_lock" (that produces dirty reads)? Or the way to go is the transaction isolation level?
there's no actual overhead in a single statement read transaction like this. Postgres uses a novel approach to MVCC.
-- john r pierce N 37, W 122 santa cruz ca mid-left coast -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general