On Tue, Mar 12, 2013 at 7:13 AM, Misa Simic <misa.simic@xxxxxxxxx> wrote:
Unless you are running an ancient version of PostgreSQL (<8.1), this would no longer pose a problem.
Cheers,
Jeff
Hi,Researching deeply my problem with concurrent processing i have found:"The more likely suspect is a foreign key conflict.Are both transactions inserting/updating rows that could reference
the same row(s) in a master table?" - Tom LaneThis is exactly the case (in my case) - several connections tries to insert rows in the same table... but some columns are referenced to settings tables... and there is possibility that two rows what we want to insert reference the same row in settings table...
Unless you are running an ancient version of PostgreSQL (<8.1), this would no longer pose a problem.
Cheers,
Jeff