18.05.2021 16:22, liviuslivius wrote:
But such replica cannot became "master" database if master is
broken/unavailable?
Why? Values of generators used as flags are usually not important and are reset to
defaults by application after promoting as if primary server has been suddenly aborted
But such replica cannot became "master" database if master is
broken/unavailable?Regards,Karol Bieniaszewski
Oryginalna wiadomość Od: Dimitry Sibiryakov
Data: 18.05.2021 16:03 (GMT+01:00) Do: For discussion
among Firebird Developers Temat: Re:
[Firebird-
18.05.2021 15:33, Karol Bieniaszewski wrote:
I as as we use genertors also as settings. E.g. we change it from 1 to 0 and
back.
And in procedures or triggers we check for value in generator if it is 1 (on)
or 0 (off).
This usage is no-go in master-slave setting because the procedures and tr
>> Sorry for the blind noise.
It is not noise.
Is there a way to configure replication to always replicate generator change?
I as as we use genertors also as settings. E.g. we change it from 1 to 0 and
back.
And in procedures or triggers we check for value in generator if it is 1 (on)
or 0 (o
30.04.2014 6:45, liviusliv...@poczta.onet.pl wrote:
> If we talking about synchronous replication then what problem with extending
> shadow files
> feature to support it?
People are asking for multimaster, not just inaccessible standby. Even
read-only
standby is not going to work with shadow
Hi,
If we talking about synchronous replication then what problem with extending
shadow files feature to support it?
Regards,
Karol Bieniaszewski
- Reply message -
Od: "Jim Starkey"
Do:
Temat: [Firebird-devel] Replication
Data: śr., kwi 30, 2014 00:46
On 4/29/2014 8:38 AM, Dimitry S