Re: INSERT ... ON CONFLICT UPDATE/IGNORE 4.0

From: Peter Geoghegan <pg(at)heroku(dot)com>
To: hlinnaka <hlinnaka(at)iki(dot)fi>
Cc: Andres Freund <andres(at)anarazel(dot)de>, Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, Stephen Frost <sfrost(at)snowman(dot)net>, Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: INSERT ... ON CONFLICT UPDATE/IGNORE 4.0
Date: 2015-05-01 21:07:06
Message-ID: CAM3SWZRgjjFu+MZc8jv=e-SgAo2Toy+Nz=rQ02Stpgv8719LHg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin pgsql-hackers

On Fri, May 1, 2015 at 7:47 AM, Heikki Linnakangas <hlinnaka(at)iki(dot)fi> wrote:
> Hmm, so it was stuck for half an hour at that point? Why do you think it was
> a livelock?
>
>> This is the same server that I shared credentials with you for. Feel
>> free to ssh in and investigate it yourself.
>
>
> I logged in, but the system seems very unresponsive in general. I just
> started "apt-get install gdb" on it, to investigate what the backends are
> stuck at. It's been running for about 30 minutes now, and I'm still
> waiting...

To be honest, I just assumed it was a livelock - maybe I should have
avoided the word. It's possible that there was an issue on the AWS
instance, too. It was disconcerting how each run of the test could
take 4 seconds or 30 seconds, with no particular pattern to it. This
was something I saw consistently.

--
Peter Geoghegan

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Marc Fromm 2015-05-01 22:39:52 migrating to 9.2 created blank dbs
Previous Message Keith 2015-05-01 20:47:32 Re: pg_dump and pg_restore with multiple streams does Not seem to improve overall times

Browse pgsql-hackers by date

  From Date Subject
Next Message Jim Nasby 2015-05-01 21:27:58 Re: Broken handling of NULLs in TG_ARGV
Previous Message Jim Nasby 2015-05-01 21:02:55 Re: Loss of some parts of the function definition