On 17 September 2015 at 15:17, Sylvain MARECHAL
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 ov
Sylvain MARECHAL 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 la
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
Sylvain MARECHAL wrote:
> Hello all,
>
> To avoid replication of some tables, I use a specific replication set.
> For example, with 2 nodes 'node1' and 'node2' and a table 'test' which
> content shall not be replicated, I do the following:
>
> mydb=# CREATE TABLE test (i INT PRIMARY KEY NOT NULL)
Hello all,
To avoid replication of some tables, I use a specific replication set.
For example, with 2 nodes 'node1' and 'node2' and a table 'test' which
content shall not be replicated, I do the following:
mydb=# CREATE TABLE test (i INT PRIMARY KEY NOT NULL);
mydb=# SELECT bdr.table_set_repli
