[PERFORM] Locking concurrency: select for update vs update

Hello, I have two tables phone_number and phone_number_type When I start transaction and insert phone_number using FK from phone_number_type. Then I can during another TX update row from phone_number_type, but I can't execute select for update on it. In db stats I see during inserInto Access

Re: [PERFORM] Locking concurrency: select for update vs update

fine UPDATE phone_number_type SET val=val+1 WHERE id_phone_number_type=500 W dniu 2016-06-07 o 09:35, Szymon Lipiński pisze: On 7 June 2016 at 09:31, Streamsoft - Mirek Szajowski mailto:m.szajow...@streamsoft.pl>> wrote: Hello, I have two tables phone_number and phone_numbe

Re: [PERFORM] Locking concurrency: select for update vs update

Thanks after your description I found select name from phone_number_type WHERE id_phone_number_type=4 for *NO KEY* update (Postgresql 9.3 ) W dniu 2016-06-07 o 15:24, Tom Lane pisze: Streamsoft - Mirek Szajowski writes: Why I can't execute 'select for update' but I can upd