Dimitry Sibiryakov

Results 114 comments of Dimitry Sibiryakov

Restore service must rely on crypt plugin name instead of key holder name

Backup part is described in #7943.

Error: database file appears corrupted after restore from backup (FB5, RC2)

Is restore with gbak ok? Can you share core dumps of crashed server?

Error: database file appears corrupted after restore from backup (FB5, RC2)

Do error happen when all servers but v5 are stopped?

Error: database file appears corrupted after restore from backup (FB5, RC2)

At this point you can attach debugger to it to see what's happening.

Preserve original values of timestamp attribute for all files that are generated in FB snapshots (which can be downloaded via "Actions" page in github)

AFAIU the problem is that there is no way to distinguish two different CI artifacts during day because build number is raised only once a day. Setting time to version...

Preserve original values of timestamp attribute for all files that are generated in FB snapshots (which can be downloaded via "Actions" page in github)

QA scripts already use Python and PowerShell so it is possible to get version from file directly (https://devblogs.microsoft.com/oldnewthing/20180529-00/?p=98855) but because of too seldom version increase it is useless. Perhaps Pavel...

[gstat] add option to analyze all pages in the database

IBSurgeon offers a database analyzer. There is no point to spoil their business.

[gstat] add option to analyze all pages in the database

> do you mean `IBAnalyst`? No, I mean DBInfo: ![dbinfo](https://github.com/FirebirdSQL/firebird/assets/17592921/c6ab2057-a921-44e2-9958-1dac0371f3e9)

Firebird 3.0, 4.0 and 5.0 Windows installers do not set the SYSDBA password if it was previously installed (even if not currently installed)

I still think that the problem is in SRP auth plugin which must either create necessary tables at first access or/and return normal "user not found" error.

replication in line command to merge replication side any time I want.(assincronous)

Isn't it exactly purpose of journal_archive_command setting? To let you do whatever you like before, after and during (or instead of) journal delivery to replica.