| 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-04-28 06:02:17 |
| Message-ID: | CAM3SWZR9RNzQS7prmU0mt4mZ8CQ7f4+UP-vvbT87y8CT_SLFxQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin pgsql-hackers |
On Mon, Apr 27, 2015 at 8:31 PM, Heikki Linnakangas <hlinnaka(at)iki(dot)fi> wrote:
> I thought we had an ironclad scheme to prevent deadlocks like this, so I'd
> like to understand why that happens.
Okay. I think I know how it happens (I was always skeptical of the
idea that this would be 100% reliable), but I'll be able to show you
exactly how tomorrow. I'll have pg_xlogdump output then.
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2015-04-28 06:49:39 | Re: INSERT ... ON CONFLICT UPDATE/IGNORE 4.0 |
| Previous Message | Harshad Adalkonda | 2015-04-28 05:47:32 | Re: server doesn't listen postgresql 9.1 after service change |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sawada Masahiko | 2015-04-28 06:14:11 | Re: Auditing extension for PostgreSQL (Take 2) |
| Previous Message | Abhijit Menon-Sen | 2015-04-28 04:56:54 | Re: basebackups during ALTER DATABASE ... SET TABLESPACE ... not safe? |