Re: [Firebird-devel] Replication Rename Error

2021-05-17 Thread Dmitry Yemanov
17.05.2021 16:29, Nils Bödeker wrote: Under parallel writing we get the following error in the replication log (sometimes, not always): FIREBIRD-4 (origin) Sat May 15 12:11:23 2021 Database: D:\NBS_DATABASE\MINICMS.GDB ERROR: Log file

Re: [Firebird-devel] 4.0 replication - One primary database with two modes

2021-05-17 Thread liviuslivius
For me configuration error should prevent with working with database at all.Consider two entries with same alias but different path this is critical configuration error and silently ignore it is not good.Regards,Karol Bieniaszewski Oryginalna wiadomość Od: Mark Rotteveel

[Firebird-devel] Replication Rename Error

2021-05-17 Thread Nils Bödeker
Hello We observer an possible replicate bug. Under parallel writing we get the following error in the replication log (sometimes, not always): FIREBIRD-4 (origin) Sat May 15 12:11:23 2021 Database: D:\NBS_DATABASE\MINICMS.GDB

Re: [Firebird-devel] 4.0 replication - One primary database with two modes

2021-05-17 Thread Mark Rotteveel
On 17-05-2021 11:33, Dmitry Yemanov wrote: Yes, the first wins. I'm wondering, however, wouldn't it be better to raise an error for multiple configurations detected for the current database? Or maybe just log a warning and keep using the first entry. I'm on the fence, it's a configuration

Re: [Firebird-devel] 4.0 replication - One primary database with two modes

2021-05-17 Thread Dmitry Yemanov
17.05.2021 12:47, Dimitry Sibiryakov wrote: Yes, the first wins. I'm wondering, however, wouldn't it be better to raise an error for multiple configurations detected for the current database? Or maybe just log a warning and keep using the first entry. Synchronous replication can work with

Re: [Firebird-devel] 4.0 replication - One primary database with two modes

2021-05-17 Thread Gabor Boros
2021.05.17. 11:31 keltezéssel, Dmitry Yemanov írta: You may specify both sync and async settings inside the same (single) database entry. Dmitry One entry for one database with two modes. Thank you Dmitry! It works! :-) Gabor Firebird-Devel mailing list, web interface at

Re: [Firebird-devel] 4.0 replication - One primary database with two modes

2021-05-17 Thread Dimitry Sibiryakov
17.05.2021 11:33, Dmitry Yemanov wrote: Yes, the first wins. I'm wondering, however, wouldn't it be better to raise an error for multiple configurations detected for the current database? Or maybe just log a warning and keep using the first entry. Synchronous replication can work with

Re: [Firebird-devel] 4.0 replication - One primary database with two modes

2021-05-17 Thread Dmitry Yemanov
17.05.2021 12:19, Mark Rotteveel wrote: This is an impossible configuration: you're defining two sets of configuration for `C:\R\DB\ORIGINAL.FDB`. You should have only one entry for a database in databases.conf. Correct. I'm not sure if the first or the last one wins, but based on your

Re: [Firebird-devel] 4.0 replication - One primary database with two modes

2021-05-17 Thread Dmitry Yemanov
17.05.2021 12:02, Gabor Boros wrote: Only one mode works in the same time per database? You may specify both sync and async settings inside the same (single) database entry. Dmitry Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel

Re: [Firebird-devel] 4.0 replication - One primary database with two modes

2021-05-17 Thread Mark Rotteveel
On 17-05-2021 11:02, Gabor Boros wrote: With the next configuration only REPLICA_ASYNC.FDB have the changes of ORIGINAL.FDB. database = C:\R\DB\ORIGINAL.FDB { journal_directory = C:\R\JD journal_archive_directory = C:\R\JAD journal_archive_timeout = 10 } database =

[Firebird-devel] 4.0 replication - One primary database with two modes

2021-05-17 Thread Gabor Boros
Hi All, With the next configuration only REPLICA_ASYNC.FDB have the changes of ORIGINAL.FDB. database = C:\R\DB\ORIGINAL.FDB { journal_directory = C:\R\JD journal_archive_directory = C:\R\JAD journal_archive_timeout = 10 } database = C:\R\DB\REPLICA_ASYNC.FDB {