Re: INSERT .. ON CONFLICT DO SELECT [FOR ..]

From: Marko Tiikkaja <marko(at)joh(dot)to>
To: Peter Geoghegan <pg(at)bowt(dot)ie>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: INSERT .. ON CONFLICT DO SELECT [FOR ..]
Date: 2017-08-15 07:17:51
Message-ID: CAL9smLAickh=rNLtw8mKkx9pi4PV1Th5VLpi3ozzbxnoG-t8Qw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Aug 15, 2017 at 7:43 AM, Peter Geoghegan <pg(at)bowt(dot)ie> wrote:

> On Mon, Aug 14, 2017 at 6:23 PM, Marko Tiikkaja <marko(at)joh(dot)to> wrote:
> > Attached is a patch for $SUBJECT. It might still be a bit rough around
> the
> > edges and probably light on docs and testing, but I thought I'd post it
> > anyway so I won't forget.
>
> Is it possible for ON CONFLICT DO SELECT to raise a cardinality
> violation error? Why or why not?

No. I don't see when that would need to happen. But I'm guessing you have
a case in mind?

.m

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Masahiko Sawada 2017-08-15 07:38:25 Re: Explicit relation name in VACUUM VERBOSE log
Previous Message Michael Paquier 2017-08-15 07:05:32 Re: [Proposal] Allow users to specify multiple tables in VACUUM commands