On 03.01.2011 18:29, Simon Riggs wrote:
> On Mon, 2011-01-03 at 18:08 +0200, Heikki Linnakangas wrote:
>> It works in read committed mode, because you acquire a new snapshot
>> after the LOCK TABLE, and anyone else who modified the table must commit
>> before the lock is granted. In serializable mode you get a serialization
> If its not safe without this
> LOCK TABLE ... IN SHARE ROW EXCLUSIVE MODE
> then we should do that automatically, and document that.
No we should not. The SQL standard doesn't require that, and it would
unnecessarily restrict concurrent updates on unrelated rows in the table.
In response to
pgsql-hackers by date
|Next:||From: Florian Pflug||Date: 2011-01-03 16:36:25|
|Subject: Re: Re: new patch of MERGE (merge_204) & a question about duplicated ctid|
|Previous:||From: Stephen Frost||Date: 2011-01-03 16:29:46|
|Subject: Re: Scanning pg_tablespace from walsender|