Improvements in the database server 5.7.07

The latest update contains some new features and important bug fixes that increase the reliability of the database server.

At this point it should be mentioned again that the current server can also be used together with older clients such as 5.5 or 5.6 (with all client versions from 4.7).


Shorter update interval

Previously, there was a standard interval of 60 seconds between two update events in which changed data was written from the cache to the database. Shortening this interval to 30 seconds leads to a better distribution of write operations over time. The I/O volume per update event is reduced, resulting in fewer heavy load peaks on the storage unit.

Acceleration of cache recovery

The reading of the cache content after opening the database has been accelerated. By combining I/O operations, an increase in speed by a factor of 3 to 10 is achieved in most cases. Update events now also take place during a longer read-in process; previously the cache recovery blocked the updates.

Preload the cache

If no valid .cache file is found for the cache restore, the entire database can optionally be read into the buffer. This option must be set separately in the database configuration of the server (the option is switched off by default). If the buffer is smaller than the database content, segments with a higher access probability (tree roots and nodes) are primarily loaded into the buffer. This option is useful if either the cache is similar in size to the database or the cache size is several gigabytes – in this case, filling the cache through normal database operations can take hours or days.

Hot standby synchronization

Update events are now also active during HSB synchronization. As the database is in read-only mode during synchronization, the update data is written to the current .tl file (just like during a backup event). This improvement is particularly important for a longer synchronization to avoid data loss in the event of a server failure during this process.

If a synchronization is started directly after opening the database, the cache recovery is also carried out at the same time, as the entire database is read anyway.

With an HSB configuration, the database is now always opened in read-only mode first. Only after checking the synchronization status is the database switched to write mode. This avoids unnecessary synchronization processes that could occur if the database was immediately switched to read-only mode after being opened in read-write mode.

Error correction during rollback

With all previous 5.7 server versions, the error entry “Transaction log file TL? has no valid blocks” could occur after opening an incomplete database during rollback, even though valid data is available in the .tl file. In extreme cases, database errors could be detected during the subsequent diagnosis with Recover or data loss could occur. This error should therefore be classified as critical. To avoid such a situation, we recommend updating all installed 5.7 servers to version 5.7.07.

Klicken Sie hier, um die Nutzungsbedingungen für unseren Blog zu lesen.

Leave a Reply

Your email address will not be published. Required fields are marked *

Leave the field below empty!

Requests, questions or feedback are welcome:

Terms of use of the comment function in the blog

1. General information

Vectorsoft AG (‘Provider’) provides a public blog for Internet users (‘Users’) on the vectorsoft.de website. The public blog is intended for the exchange of information and ideas. Users who participate with contributions and comments undertake to comply with the blog terms of use and are responsible for the accuracy, appropriateness and freedom from legal infringements of their contributions. By using the comment function in our blog, you accept these terms of use.

2. Netiquette

We ask you to refrain from personal attacks and provocations based on other opinions. Please argue objectively and maintain a constructive discussion culture. Your comment should always be related to the topic in question in order to avoid digressions into other topics. Posting the same comment or several similar comments more than once is not permitted.

3. Prohibition of illegal content

By submitting your comment, you confirm that you are not violating any copyrights or other rights of third parties. Inciting, racist statements, instructions for criminal offences and their glorification, depictions of violence, pornographic content and statements that violate personal rights are prohibited.

4. No advertising

The use of the comment function is not permitted for commercial or party-political purposes. Advertising contributions of any kind will be deleted immediately.

5. Details of the name

When entering your name, pay attention to the principles mentioned above.

6. Source references

If you intend to publish quotes or contributions from third parties, please indicate the respective sources and explain how they relate to the blog post.

7. Violation of the terms of use

Posts that violate this policy will be deleted immediately. If you notice any violations yourself, please send us the link to the comment in question by e-mail to . We expressly point out that we will exclude individual users in the event of repeated or serious violations of these terms of use.

As of: Sept. 2024

Get your Trial Version now!

Test yeet free of charge

IHRE EVALUIERUNGSLIZENZ - JETZT ANFORDERN!

TESTEN SIE DIE CONZEPT 16 VOLLVERSION - UNVERBINDLICH und KOSTENFREI

Subscribe to our newsletter

[cleverreach_signup]
WordPress Cookie Notice by Real Cookie Banner