Re: [GENERAL] Counterintuitive locking behavior

Chris Travers wrote on 06.01.2013 03:18: i.e. where on UPDATE foo, all rows selected from foo during the update are locked unless the subselect specifically states otherwise. That would strike *me* as wrong. The UPDATE should only lock the rows that were actually updated, not those that were

[GENERAL] currval of sequence xxx_seq is not yet defined in this session?

HI,everybody: recently i found some errors in pg_log when i do some pressure testing,looks like "2013-01-05 21:48:29.870 CST,"postgres","wedding",15850,"172.25.10.28:37100",50e82f2d.3dea,1,"SELECT",2013-01-05 21:48:29 CST,19/80509,0,ERROR,55000,"currval of sequence ""t_wedding_wedding_id_seq"" i