Postgres Pro
Downloads
Home   >   mailing lists

Re: improving foreign key locks - Mailing list pgsql-hackers

From Jim Nasby
Subject Re: improving foreign key locks
Date
Msg-id 5DF35D5E-53B4-4D12-8652-8FA3823567D1@nasby.net
Whole thread Raw
In response to Re: improving foreign key locks  (Florian Pflug <fgp@phlo.org>)
Responses Re: improving foreign key locks  (Florian Pflug <fgp@phlo.org>)
List pgsql-hackers
Tree view 
On Dec 1, 2010, at 11:09 AM, Florian Pflug wrote:
> An UPDATE on such a SHARE locked row would be allowed despite the lock if it only changed columns not mentioned by
anyunique index. 

On a side-note, by "changed columns" do you mean the column appeared in the UPDATE statement, or the data actually
changed?I suspect the former might be easier to implement, but it's really going to fsck with some applications (Rails
isone example that comes to mind). 
--
Jim C. Nasby, Database Architect                   jim@nasby.net
512.569.9461 (cell)                         http://jim.nasby.net

pgsql-hackers by date:

Previous
From: Jim Nasby
Date:
Subject: Re: crash-safe visibility map, take three
Next
From: Jim Nasby
Date:
Subject: Re: FK's to refer to rows in inheritance child