Percona

APRIL 1, 2024

ProxySQL recently released version 2.6.0, and going through the release notes, I focused on the following:Added support for caching_sha2_password!This is great news for the community! The caching_sha2_password authentication method for frontend connections is now available. This has been a long-awaited feature …Why?Because in MySQL 8, caching_sha2_password has been the default authentication method.

Availability 99

Availability 99

Percona Community

APRIL 1, 2024

Percona software releases and updates March 18 - April 2, 2024. Percona is a leading provider of unbiased, performance-first, open source database solutions that allow organizations to easily, securely, and affordably maintain business agility, minimize risks, and stay competitive, free from vendor lock-in. Percona software is designed for peak performance, uncompromised security, limitless scalability, and disaster-proofed availability.

Open Source 58

Open Source Scalability Database Software 58

Percona

APRIL 1, 2024

Percona’s pg_tde project brings a long-needed ability to encrypt data to PostgreSQL transparently. We are actively asking you to test this code to help build a better project. So please test pg_tde!As you have probably read in earlier blogs on pg_tde, it depends on a keyring.Two keysEncrypting the data requires two types of keys.

Testing 90

Testing Code Software Software 90

Kovair

APRIL 1, 2024

Get information on - The Importance of Accessibility Testing in Software Development, follow Kovair Blog for the latest information and updates on software development and information technology.

Software 52

Software Software Development Testing 52

Percona

APRIL 1, 2024

This blog was originally published in June 2022 and was updated in April 2024.PostgreSQL’s built-in autovacuum – the housekeeper – is improving, version after version. It is becoming more capable while reducing its overhead and addressing edge cases.

Tuning 72

Tuning Performance 72

n0derunner

APRIL 1, 2024

Running iperf with parallel threads TL;DR – When running iperf with parallel threads/workers the -P option must be specified after the -c <target-IP> option. This is mentioned in the manpage but some options (-t for instance) work in any order, while others (specifically the -P for parallel threads) definitely does not, which is a bit … The post Using iperf multi-stream may not work as expected appeared first on n0derunner.

C++ 40

C++ Network 40