Re: Slow concurrent processing

From: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>
To: Misa Simic <misa(dot)simic(at)gmail(dot)com>
Cc: "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org>
Subject: Re: Slow concurrent processing
Date: 2013-03-12 17:09:21
Message-ID: CAMkU=1zune_RMF=2k46b_QwJ6C=E73deNzixSmEfdyd7ORGa3A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On Tue, Mar 12, 2013 at 7:13 AM, Misa Simic <misa(dot)simic(at)gmail(dot)com> wrote:

> Hi,
>
> Researching deeply my problem with concurrent processing i have found:
>
>
> http://postgresql.1045698.n5.nabble.com/WHY-transaction-waits-for-another-transaction-tp2142627p2142630.html
>
>
> "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 Lane
>
> This 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

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Misa Simic 2013-03-12 17:11:46 Re: Slow concurrent processing
Previous Message Steve Crawford 2013-03-12 15:54:57 Re: Slow concurrent processing