Postgres Pro
Downloads
Home   >   mailing lists

Re: ON CONFLICT DO UPDATE for partitioned tables - Mailing list pgsql-hackers

From Pavan Deolasee
Subject Re: ON CONFLICT DO UPDATE for partitioned tables
Date
Msg-id CABOikdNMqDsc9GFSvpAiWB5tm6sTTkAaozbwkRB2e2UqOQ8zsg@mail.gmail.com
Whole thread Raw
In response to Re: ON CONFLICT DO UPDATE for partitioned tables  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Responses Re: ON CONFLICT DO UPDATE for partitioned tables  (Etsuro Fujita <fujita.etsuro@lab.ntt.co.jp>)
List pgsql-hackers
Tree view


On Fri, Mar 2, 2018 at 9:06 PM, Alvaro Herrera <alvherre@2ndquadrant.com> wrote:


@@ -106,6 +120,9 @@ typedef struct PartitionTupleRouting
    int         num_subplan_partition_offsets;
    TupleTableSlot *partition_tuple_slot;
    TupleTableSlot *root_tuple_slot;
+   List      **partition_arbiter_indexes;
+   TupleTableSlot **partition_conflproj_slots;
+   TupleTableSlot **partition_existing_slots;
 } PartitionTupleRouting;


I am curious why you decided to add these members to PartitionTupleRouting structure. Wouldn't ResultRelationInfo be a better place to track these or is there some rule that we follow?

Thanks,
Pavan

--
 Pavan Deolasee                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services

pgsql-hackers by date:

Previous
From: Arthur Zakirov
Date:
Subject: Re: pg_get_functiondef forgets about most GUC_LIST_INPUT GUCs
Next
From: Ashutosh Bapat
Date:
Subject: Re: [HACKERS] Another oddity in handling of WCO constraints in postgres_fdw