Re: BDR truncate and replication sets - Mailing list pgsql-general

From Craig Ringer
Subject Re: BDR truncate and replication sets
Date
Msg-id CAMsr+YHxx46g99QDecSq-bps8xF2FVa9PynaEqSpRAetfGBpEw@mail.gmail.com
Whole thread Raw
In response to Re: BDR truncate and replication sets  (Sylvain MARECHAL <marechal.sylvain2@gmail.com>)
List pgsql-general
On 17 September 2015 at 15:17, Sylvain MARECHAL
<marechal.sylvain2@gmail.com> wrote:
> Le 15/09/2015 18:56, Alvaro Herrera a écrit :
>>
>> Sylvain MARECHAL wrote:
>>>
>>> [...] The exception is with TRUNCATE: In case it is called, data is
>>> removed on
>>> both nodes.
>>>
>>> Is it a feature or a bug?
>>
>> I think it's an oversight.  Replication sets were added later than the
>> TRUNCATE trigger, so the design for the latter does not consider the
>> former as far as I know.
>
> Ok. May I fill a bug report?

Please.

It's clearly a bug and will need to be addressed in the next point release.


--
 Craig Ringer                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services


pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: search_path not reloaded via unix socket connections
Next
From: Craig Ringer
Date:
Subject: Re: BDR: cannot drop database even after parting the node