On Monday, November 4, 2013 3:23 PM, Adrian Klaver <adrian.klaver@xxxxxxxxx> wrote: >Probably poor choice of words:). So then, what we are looking at is >other clients trying to update user_profile but not succeeding because >pid 4899 is blocking. At this point all I can see is that the offending >query is updating some fields the others are not; disabled and reset_code. > >Is that always the case? > >If so any thing in the code path that is different when those fields are >updated? We have scenarios where exact same query is in play in all instances. Any thoughts as to the fact that this could be a full table_lock simply based on the use of username (non primary key - but specifically unique constraint) in the where clause? I'm grasping I know.... -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
