Re: [HACKERS] INSERT .. ON CONFLICT DO SELECT [FOR ..] - Mailing list pgsql-hackers

From Marko Tiikkaja
Subject Re: [HACKERS] INSERT .. ON CONFLICT DO SELECT [FOR ..]
Date
Msg-id CAL9smLAickh=rNLtw8mKkx9pi4PV1Th5VLpi3ozzbxnoG-t8Qw@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] INSERT .. ON CONFLICT DO SELECT [FOR ..]  (Peter Geoghegan <pg@bowt.ie>)
Responses Re: [HACKERS] INSERT .. ON CONFLICT DO SELECT [FOR ..]  (Peter Geoghegan <pg@bowt.ie>)
List pgsql-hackers
On Tue, Aug 15, 2017 at 7:43 AM, Peter Geoghegan <pg@bowt.ie> wrote:
On Mon, Aug 14, 2017 at 6:23 PM, Marko Tiikkaja <marko@joh.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

pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: [HACKERS] [Proposal] Allow users to specify multiple tables inVACUUM commands
Next
From: Masahiko Sawada
Date:
Subject: Re: [HACKERS] Explicit relation name in VACUUM VERBOSE log