| From: | Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com> |
|---|---|
| To: | Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk> |
| Cc: | Kevin Grittner <kgrittn(at)gmail(dot)com>, Peter Geoghegan <pg(at)bowt(dot)ie>, Craig Ringer <craig(at)2ndquadrant(dot)com>, Marko Tiikkaja <marko(at)joh(dot)to>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Transition tables vs ON CONFLICT |
| Date: | 2017-06-12 02:40:08 |
| Message-ID: | CAEepm=1ypxjBG-zhCnr2aabp86Kd_a9OppKMMUhhSyQd3yfG3g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Jun 9, 2017 at 4:10 PM, Thomas Munro
<thomas(dot)munro(at)enterprisedb(dot)com> wrote:
> On Wed, Jun 7, 2017 at 10:47 AM, Peter Geoghegan <pg(at)bowt(dot)ie> wrote:
>> I suppose you'll need two tuplestores for the ON CONFLICT DO UPDATE
>> case -- one for updated tuples, and the other for inserted tuples.
>
> [...]
>
> Here is a patch implementing the above. It should be applied on top
> of transition-tuples-from-wctes-v2.patch[2].
Here's a new version of patch #3. It's rebased on top of
transition-tuples-from-wctes-v3.patch. I also moved a comment for
execReplication.c out of this patch into patch #2, correcting a
mistake in my pancake stacking.
--
Thomas Munro
http://www.enterprisedb.com
| Attachment | Content-Type | Size |
|---|---|---|
| transition-tuples-from-on-conflict-v2.patch | application/octet-stream | 11.4 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeevan Ladhe | 2017-06-12 02:59:30 | Re: Adding support for Default partition in partitioning |
| Previous Message | Thomas Munro | 2017-06-12 02:38:19 | Re: PG10 transition tables, wCTEs and multiple operations on the same table |