| From: | Craig Ringer <craig(at)2ndquadrant(dot)com> |
|---|---|
| To: | Sylvain MARECHAL <marechal(dot)sylvain2(at)gmail(dot)com> |
| Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: BDR truncate and replication sets |
| Date: | 2015-09-18 05:44:50 |
| Message-ID: | CAMsr+YHxx46g99QDecSq-bps8xF2FVa9PynaEqSpRAetfGBpEw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 17 September 2015 at 15:17, Sylvain MARECHAL
<marechal(dot)sylvain2(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Craig Ringer | 2015-09-18 06:00:48 | Re: BDR: cannot drop database even after parting the node |
| Previous Message | Tom Lane | 2015-09-18 03:31:00 | Re: search_path not reloaded via unix socket connections |