Andrej Kirejeŭ
Andrej Kirejeŭ
And regarding failed gfix. The firebird.log now contains thousands of records like: > XXXX Tue Jan 2 13:16:27 2024 Database: XXXX Error: Record 3 is wrong length in table GD_EMPLOYEE...
The database was backed up on FB 3 server and restored on FB 5.
There are no suspicious records in the Windows's logs. So, I assume that FB5 service didn't crash.
> Do error happen when all servers but v5 are stopped? cann't check right now. those servers being used.
well, I'm trying to run from the command prompt and the command just hangs. no CPU activity, no records in the firebird.log file. ``` C:\Program Files\FB5>gbak -r "K:\Bases\xxx.bk" "g:\Bases\xxx.fdb" -user...
restoring of metadata goes without any problems: ``` gbak:gbak version WI-V5.0.0.1304 Firebird 5.0 RC 2 gbak:use up to 8 parallel workers gbak:transportable backup -- data in XDR format gbak: backup...
now, I will start restoring using gbak utility with -se switch.
Is it hard to merge this PR? We desperately need in ability to stop attempts to create resource (attach to database in our case) after first try failed.
Consider we are pooling connections to db server. Somehow wrong login/password were specified. Current behavior is that the library will try to reconnect again and again... Correct work in this...
Callback `factoryCreateError`would be useful if we could: 1. know exactly which acquire call fails 2. stop further attempts 3. bubble up exception to a calling code