"Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote
> Right, the snapshot does not become set until you do a non-utility
> command (normally, SELECT/INSERT/UPDATE/DELETE). This is a feature, not
> a bug, because it lets the transaction take table locks before its
> snapshot becomes set.
Hm, mostly I understand it as an optimization. What do you mean by "it lets
the transaction take table locks before its snapshot becomes set"? If we
take a snapshot at BEGIN, then the transaction can't take table locks?
test=# begin;select count(*) from k;
test=# lock table k;
In response to
pgsql-general by date
|Next:||From: Tom Lane||Date: 2006-06-30 02:27:02|
|Subject: Re: Strange Behavior with Serializable Transcations |
|Previous:||From: Tim Hart||Date: 2006-06-29 21:58:23|
|Subject: Re: User privileges in web database applications|