[Percona Community Forum] Summary

No dark-mode styles — this email renders the same in a dark client.

A brief summary of [Percona Community Forum][1] since 2026-09-07 00:14:03 UTC

9 New Topics
12 New Users


  
  ### Popular Topics

    [Pg_tde_archive_decrypt/pg_tde_restore_encrypt limitation in pgbackrest][2]

      @grill 
The limitation:- Limitations of pg_tde - Percona Transparent Data Encryption for PostgreSQL mentions that the following options should be set in PgBackRest to allow pg_tde WAL encryption. 
Need to Configure/Enable: 
pg_tde_archive_decrypt 
`pg_tde_restore_encrypt 
Need to disable them: 
archive-async 
archive-header-check 
checksum-page 
PgBackRest will still work if you are not using the WAL encryption option; however, if you want to apply it, then it must be configured as mentioned above. The underlying tool, PgBackRest itself, doesn’t need to know about the encryption or decryption mechanism. The tool will simply recognise the WALs once they are decrypted by the pg_tde process. 
E.g, 
archive_command='pg_tde_archive_decrypt %f %p "pgbackrest --stanza=your_stanza archive-push %%p"'


Yes, other external tools can use the WAL unless they are managed by the pg_tde wal encryption.

    
    [Does Percona MySQL support arbitrator‑node capability][3]

      Hello @Leo_Ma, 
lightweight arbitrator functionality already exists in Percona XtraDB Cluster. Since Group Replication is an upstream project, I doubt we would be adding new functionality to a “competing” clustering solution. If arbitrator nodes are something you need in your architecture, I strongly recommend you look at the more mature XtraDB Cluster solution.

    
    [Reaching for pg_repack, pg_squeeze, or VACUUM FULL first is usually the wrong move , change my mind][4]

      Reclaiming disk space when you’re already out of disk space ; what’s the right order of operations? 
This comes up often enough that I want to hear how others actually handle it, because the standard advice has a chicken-and-egg problem. 
The scenario: heavily bloated tables from accumulated dead tuples, plus a pile of indexes that may or may not be earning their keep, and not much free space on the volume. The usual recommendations are pg_repack, pg_squeeze, or VACUUM FULL but all three want temporary space you don’t have. pg_repack in particular needs a new table, new indexes, and a log table for changes during the copy, so peak usage can exceed VACUUM FULL. You reach for it to avoid the ACCESS EXCLUSIVE lock and get surprised by the disk cost instead. 
A few things I’d like to argue out: 
1. Is dropping unused indexes always the correct first move? It’s the only step that returns space with no temporary copy. But idx_scan = 0 in pg_stat_user_indexes isn’t proof stats reset, replicas...

    
    [PG Operator 3.0.0+ compatibility with certified pgBackRest images][5]

      Description:
The percona/percona-pgbackrest:2.58.0-2 image is mentioned in the Percona certified images documentation for the operator v3.0.0. 
Unfortunately, using this image is blocked by a fatal mismatch between the pgbackrest path used by the operator (/opt/crunchy/bin/pgbackrest) and the actual path in the image (/usr/bin/pgbackrest). As a result, the backup container fails with the following error: 
Error: failed to create containerd task: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: exec: "/opt/crunchy/bin/pgbackrest": stat /opt/crunchy/bin/pgbackrest: no such file or directory 
I tried this with 3.1.0 with the same result. Am I missing something important? It looks like a working image for 3.0.0 does not exist and backups are broken, but I haven’t found any related open issues in the operator repo or Percona Jira, despite it being a pretty critical function. 
Steps to Reproduce:
Percon...

    
    [PMM password policy][6]

      We use PMM for our monitoring solutions. For a security compliance we have been asked about the password policy of our user creation in PMM. request you to share us the password policy or if the feature will arrive at a later version for the same.

    

  




**New for you**

* [Percona Server 5.7 - ERROR 3185 on one DRE encrypted table only; others work fine][7] - 1 - [Percona Server for MySQL 5.7]
* [A Fail-Fast PostgreSQL Migration Preflight for CI | Percona Community][8] - 1 - [Community website]
* [ProxySQL HA with BGP ECMP Anycast | Percona Community][9] - 1 - [Community website]
* [The Perfect Serve: What Tennis Taught Me About Reading PMM … | Percona Community][10] - 1 - [Community website]



[1]: https://forums.percona.com/
[2]: https://forums.percona.com/t/pg-tde-archive-decrypt-pg-tde-restore-encrypt-limitation-in-pgbackrest/41250
[3]: https://forums.percona.com/t/does-percona-mysql-support-arbitrator-node-capability/41246
[4]: https://forums.percona.com/t/reaching-for-pg-repack-pg-squeeze-or-vacuum-full-first-is-usually-the-wrong-move-change-my-mind/41251
[5]: https://forums.percona.com/t/pg-operator-3-0-0-compatibility-with-certified-pgbackrest-images/41259
[6]: https://forums.percona.com/t/pmm-password-policy/41248
[7]: https://forums.percona.com/t/percona-server-5-7-error-3185-on-one-dre-encrypted-table-only-others-work-fine/41255
[8]: https://forums.percona.com/t/a-fail-fast-postgresql-migration-preflight-for-ci-percona-community/41252
[9]: https://forums.percona.com/t/proxysql-ha-with-bgp-ecmp-anycast-percona-community/41249
[10]: https://forums.percona.com/t/the-perfect-serve-what-tennis-taught-me-about-reading-pmm-percona-community/41260
[11]: https://forums.percona.com/



  This summary is sent from [Percona Community Forum][11] when we haven't seen you in a while. Change [your email settings][12], or [click here][13] to unsubscribe.

[12]: https://forums.percona.com/my/preferences/emails
[13]: https://forums.percona.com/email/unsubscribe/b7d634a8bcd3f86133e184f0d28b26373e4493e4aa7031c4c805edeec8c9243a

Accession

nse/percona/2026-09-14/1426

From

Percona Community Forum · notifications@percona1.discoursemail.com

Sent

14 September 2026 · 00:00 UTC