Re: [PATCH] Logical decoding of TRUNCATE

From: Andres Freund <andres(at)anarazel(dot)de>
To: Marco Nenciarini <marco(dot)nenciarini(at)2ndquadrant(dot)it>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [PATCH] Logical decoding of TRUNCATE
Date: 2017-12-29 19:55:36
Message-ID: 20171229195536.cdzmgllfkln6wo6t@alap3.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general 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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Francis Santiago 2017-12-29 21:48:32 Re: Oacle to Postgres migration
Previous Message chiru r 2017-12-29 19:35:27 Re: PgBackRest question?

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2017-12-29 20:38:18 Re: [HACKERS] Proposal: Local indexes for partitioned table
Previous Message Andres Freund 2017-12-29 19:38:43 Re: Condition variable live lock