Re: [PATCH] Logical decoding of TRUNCATE

From: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
To: Petr Jelinek <petr(dot)jelinek(at)2ndquadrant(dot)com>, Marco Nenciarini <marco(dot)nenciarini(at)2ndquadrant(dot)it>, Simon Riggs <simon(at)2ndquadrant(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [PATCH] Logical decoding of TRUNCATE
Date: 2018-01-24 12:50:10
Message-ID: 5462dc00-4941-167e-b287-d7bd9b2283e9@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

I wonder whether this should be dealing with sequences at all. We are
not currently publishing any information about sequences, so it seems
weird to do it only here. Also, I'd imagine that if we ever get to
publishing sequence events, then the sequence restarts would be
published as independent events.

--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Petr Jelinek 2018-01-24 12:53:50 Re: [PATCH] Logical decoding of TRUNCATE
Previous Message Vincenzo Romano 2018-01-24 12:11:47 Re: PostgreSQL 9.6: view based on sequence

Browse pgsql-hackers by date

  From Date Subject
Next Message Petr Jelinek 2018-01-24 12:53:50 Re: [PATCH] Logical decoding of TRUNCATE
Previous Message Petr Jelinek 2018-01-24 12:44:47 Re: Is it valid to have logical replication between 2 databases on the same postgres server?