On Tue, Feb 13, 2018 at 5:25 AM, Peter Eisentraut
wrote:
> On 2/8/18 10:54, amul sul wrote:
>> Not really, like ExecUpdate for an update of partition key if delete is
>> failed
>> then the further insert will be skipped, but you are correct, it might be
>> more
On 2/8/18 10:54, amul sul wrote:
> Not really, like ExecUpdate for an update of partition key if delete is failed
> then the further insert will be skipped, but you are correct, it might be more
> tricky than I can think -- there is no guarantee that the next insert
> operation
> which
On Wed, Feb 7, 2018 at 6:00 PM, Amit Kapila wrote:
> On Wed, Feb 7, 2018 at 3:42 PM, amul sul wrote:
>> On Wed, Feb 7, 2018 at 3:03 PM, Amit Khandekar
>> wrote:
>>> On 7 February 2018 at 13:53, amul sul
On Wed, Feb 7, 2018 at 6:00 PM, Amit Kapila wrote:
> On Wed, Feb 7, 2018 at 3:42 PM, amul sul wrote:
>> On Wed, Feb 7, 2018 at 3:03 PM, Amit Khandekar
>> wrote:
>>> On 7 February 2018 at 13:53, amul sul
On Wed, Feb 7, 2018 at 3:42 PM, amul sul wrote:
> On Wed, Feb 7, 2018 at 3:03 PM, Amit Khandekar wrote:
>> On 7 February 2018 at 13:53, amul sul wrote:
>>> Hi,
>>>
>>> If an update of partition key involves tuple movement from one
On 7 February 2018 at 17:33, Amit Khandekar 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
On Wed, Feb 7, 2018 at 3:03 PM, Amit Khandekar wrote:
> On 7 February 2018 at 13:53, amul sul wrote:
>> Hi,
>>
>> If an update of partition key involves tuple movement from one partition to
>> another partition then there will be a separate delete on
On 7 February 2018 at 13:53, amul sul wrote:
> Hi,
>
> If an update of partition key involves tuple movement from one partition to
> another partition then there will be a separate delete on one partition and
> insert on the other partition made.
>
> In the logical replication