From: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
---|---|
To: | Robert Haas <rhaas(at)postgresql(dot)org> |
Cc: | pgsql-committers <pgsql-committers(at)postgresql(dot)org> |
Subject: | Re: pgsql: Allow UPDATE to move rows between partitions. |
Date: | 2018-01-23 13:44:18 |
Message-ID: | CAA4eK1LG01SjT5R48M5CYeHVnMP_qwMMHEhF5y96H2ro=ctdQA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers pgsql-hackers |
On Sat, Jan 20, 2018 at 2:03 AM, Robert Haas <rhaas(at)postgresql(dot)org> wrote:
> Allow UPDATE to move rows between partitions.
>
+ If an <command>UPDATE</command> on a partitioned table causes a row to move
+ to another partition, it will be performed as a <command>DELETE</command>
+ from the original partition followed by an <command>INSERT</command> into
+ the new partition. In this case, all row-level <literal>BEFORE</literal>
+ <command>UPDATE</command> triggers and all row-level
+ <literal>BEFORE</literal> <command>DELETE</command> triggers are fired on
+ the original partition.
Do we need to maintain triggers related behavior for logical
replication? In logical replication, we use ExecSimpleRelationDelete
to perform Delete operation which is not aware of this special
behavior (execute before update trigger for this case).
--
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2018-01-23 15:18:35 | pgsql: doc: simplify intermediate certificate mention in libpq docs |
Previous Message | Peter Eisentraut | 2018-01-23 12:13:35 | pgsql: Add installcheck support to more test suites |
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2018-01-23 13:51:25 | Re: [HACKERS] MERGE SQL Statement for PG11 |
Previous Message | Aleksander Alekseev | 2018-01-23 13:38:08 | Re: Flexible configuration for full-text search |