Re: ON CONFLICT does not support deferrable unique constraints

From: Francisco Olarte <folarte(at)peoplecall(dot)com>
To: Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>
Cc: Andreas Joseph Krogh <andreas(at)visena(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: ON CONFLICT does not support deferrable unique constraints
Date: 2016-08-24 16:36:16
Message-ID: CA+bJJbxpTdQ3e2Atk8UmHaEatZ9vahPSPFne8tucn+T35HtYFg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Wed, Aug 24, 2016 at 6:26 PM, Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> wrote:
> On Wed, Aug 24, 2016 at 6:05 AM, Andreas Joseph Krogh
>> Are there any plans to lift this restriction?
> I'm trying to figure out a method for making this work in my head.
> These two things seem kind of opposed to each other.

He probably wants to just treat is as non-deferrable just during the
upsert. I do not know if he has thought this opens a can of worms (
like, the constraint may be already broken due to precious DML ).

Francisco Olarte.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Andreas Joseph Krogh 2016-08-24 19:22:48 Re: ON CONFLICT does not support deferrable unique constraints
Previous Message Scott Marlowe 2016-08-24 16:26:13 Re: ON CONFLICT does not support deferrable unique constraints