| From: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
|---|---|
| To: | Amit Khandekar <amitdkhan(dot)pg(at)gmail(dot)com> |
| Cc: | amul sul <sulamul(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: In logical replication concurrent update of partition key creates a duplicate record on standby. |
| Date: | 2018-02-07 11:58:36 |
| Message-ID: | CAMsr+YE6vFbqm8FgC6DF-=qJXmx4pWBTeJr8TZNT1QrHhr16RA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 7 February 2018 at 17:33, Amit Khandekar <amitdkhan(dot)pg(at)gmail(dot)com> wrote:
>
> A quick thinking on how to resolve this makes me wonder if we can
> manage to pass some information through logical decoding that the
> delete is part of a partition key update. This is analogous to how we
> set some information locally in the tuple by setting
> tp.t_data->t_ctid.ip_blkid to InvalidBlockNumber.
>
>
We already do something similar for UPDATEs that change the REPLICA
IDENTITY; we include the oldkey in extra WAL.
The main question is whether the required knowledge is available at a
suitable level.
--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2018-02-07 12:30:01 | Re: In logical replication concurrent update of partition key creates a duplicate record on standby. |
| Previous Message | Amit Kapila | 2018-02-07 11:41:46 | Re: [HACKERS] Restrict concurrent update/delete with UPDATE of partition key |