Quick Links

Partitioning vs ON CONFLICT

From:	Thom Brown <thom(at)linux(dot)com>
To:	PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp>
Subject:	Partitioning vs ON CONFLICT
Date:	2017-02-16 14:54:00
Message-ID:	CAA-aLv7Z4uygtq-Q5CvDi9Y=VZxUyEnuWjL=EwCfOof=L04hgg@mail.gmail.com
Views:	Whole Thread \| Raw Message \| Download mbox \| Resend email
Thread:
Lists:	pgsql-hackers

Hi,

At the moment, partitioned tables have a restriction that prevents
them allowing INSERT ... ON CONFLICT ... statements:

postgres=# INSERT INTO cities SELECT 1, 'Crawley',105000 ON CONFLICT
(city_id) DO NOTHING;
ERROR: ON CONFLICT clause is not supported with partitioned tables

Why do we have such a restriction? And what would it take to remove it?

Thanks

Thom

Responses

Re: Partitioning vs ON CONFLICT at 2017-02-16 15:03:54 from Simon Riggs

Browse pgsql-hackers by date

	From	Date	Subject
Next Message	Surafel Temsgen	2017-02-16 14:58:52	Re: New CORRESPONDING clause design
Previous Message	Amit Kapila	2017-02-16 14:46:39	Re: Write Ahead Logging for Hash Indexes

Quick Links

Partitioning vs ON CONFLICT

Responses

Browse pgsql-hackers by date

pFad - (p)hone/(F)rame/(a)nonymizer/(d)eclutterfier! Saves Data!