681b9ff1cd
Just as we use pgindent to validate that our c files conform to postgres coding standards, we also run pgperltidy to do the same for perl files. We only run it on our own code in contrib/pg_tde/ This doesn't actually run pgperltidy as we need to inject some options in a way that didn't seem possible in that script. Instead it does the same thing with some slight changes. We also bump the ubuntu version for this google actions job to the newest LTS as the older ubuntu version seems to have a version of perltidy that doesn't support the options used by pgperltidy.
Percona Server for PostgreSQL
Percona Server for PostgreSQL is a free, enhanced, fully compatible, open source, drop-in replacement for the PostgreSQL Database Management System with enterprise-grade features. It requires no changes to PostgreSQL applications or code.
PostgreSQL is an advanced object-relational database management system that supports an extended subset of the SQL standard, including transactions, foreign keys, subqueries, triggers, user-defined types and functions. This distribution also contains C language bindings.
Copyright and license information can be found in the file COPYRIGHT.
General documentation about this version of Percona Server for PostgreSQL can be found at https://docs.percona.com/postgresql/17/. In particular, information about building PostgreSQL from the source code can be found at https://docs.percona.com/postgresql/17/installing.html.
Submit a bug report or a feature request
If you find a bug in Percona Server for PostgreSQL, you can submit a report to the project's Jira issue tracker
As a general rule of thumb, please try to create a bug report that is:
Reproducible - include the steps on how to reproduce the issue
Specific - include as much detail as possible, such as which version, which environment, etc.
Unique - do not duplicate existing tickets
Scoped to a single issue - only one issue per report