Re: [PATCH] Logical decoding of TRUNCATE - Mailing list pgsql-hackers

From Andres Freund
Subject Re: [PATCH] Logical decoding of TRUNCATE
Date
Msg-id 20171229195536.cdzmgllfkln6wo6t@alap3.anarazel.de
Whole thread Raw
In response to [PATCH] Logical decoding of TRUNCATE  (Marco Nenciarini <marco.nenciarini@2ndquadrant.it>)
Responses Re: [PATCH] Logical decoding of TRUNCATE  (Marco Nenciarini <marco.nenciarini@2ndquadrant.it>)
Re: [PATCH] Logical decoding of TRUNCATE  (Simon Riggs <simon@2ndquadrant.com>)
List pgsql-hackers
Hi,

On 2017-12-29 14:15:22 +0100, Marco Nenciarini wrote:
> This patch implements support for TRUNCATE statements
> in logical replication. The work has mainly done by Simon Riggs then
> finished by me. Tests are written by me.
> 
> TRUNCATE is treated as a form of DELETE for the purpose of deciding
> whether to publish, or not.

It'd be good if you explained exactly what the chosen behaviour is, and
why that's the right behaviour in comparison to other alternatives.

- Andres


pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: Condition variable live lock
Next
From: Alvaro Herrera
Date:
Subject: Re: [HACKERS] Proposal: Local indexes for partitioned table