On Wed, May 1, 2013 at 7:16 AM, Carlo Stonebanks <stonec.register@xxxxxxxxxxxx> wrote: > Very good to know, Steve. We're on 9.0 right now but I will investigate as > all the work is for unattended automatic processes which are continuously > streaming data from multiple resources and need to resolve these collisions > by themselves. If it was me, I'd be putting a 'before' statement level trigger on the table to raise a warning into the log with the backend pid assuming I could handle the volume. There are lots of ways the client could turn out to be wrong, for example client side connection poolers (which I tend to hate). Only when it's 100% proven this is a single backend case (which none of us really believe is the case including you) is further research justified. merlin -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
