![]() |
1 week ago | |
---|---|---|
.github | 1 month ago | |
ci_scripts | 2 weeks ago | |
config | 7 months ago | |
contrib | 1 week ago | |
doc | 4 months ago | |
smgr_patch | 12 months ago | |
src | 1 week ago | |
.cirrus.star | 2 years ago | |
.cirrus.tasks.yml | 4 months ago | |
.cirrus.yml | 2 years ago | |
.dir-locals.el | 7 years ago | |
.editorconfig | 6 years ago | |
.git-blame-ignore-revs | 5 months ago | |
.gitattributes | 7 months ago | |
.gitignore | 7 months ago | |
.gitmodules | 8 months ago | |
COPYRIGHT | 4 months ago | |
GNUmakefile.in | 1 year ago | |
HISTORY | 6 years ago | |
Makefile | 8 months ago | |
README.md | 4 months ago | |
aclocal.m4 | 3 years ago | |
configure | 3 months ago | |
configure.ac | 3 months ago | |
meson.build | 2 weeks ago | |
meson_options.txt | 12 months ago |
README.md
Code coverage for pg_tde: 
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