epolkerman
epolkerman
Repmgr version 5.0.0 PostgreSQL version 12.1 Standby configuration file: node_id='2' node_name='standby_node_1' conninfo='host=w.x.y.z user=repmgr dbname=repmgr connect_timeout=2' replication_user='repmgr_repl' pg_bindir='/usr/xxxx/postgres/12/bin/' data_directory='/var/xxxx/postgres/12/data' config_directory='/etc/xxxx/postgres/12/data' log_level=INFO log_facility=STDERR log_file='/var/log/xxxx/repmgr/repmgr.log' For streaming replication a dedicated user is used...
Installed pg_store_plans version 1.6.1 together with postgresql 15.1. In postgresql.conf following was added: shared_preload_libraries = 'pg_store_plans, pg_stat_statements' When trying to (re)start the postgresql server, it refuses to start: pg_ctl: could...
Compiled and installed pg_auto_failover 2.1 Checking with pg_autoctl --version gives: `> pg_autoctl --version` pg_autoctl version .dirty pg_autoctl extension version 2.1 compiled with PostgreSQL 16.3 on x86_64-pc-linux-gnu, compiled by gcc (GCC)...
Installed pg_background version 1.1 and created the extension in a PostgreSQL 15 database. Running following commands works with version 1.1 of the extension: ``` postgres=# SELECT pg_background_launch('select firstname from name');...
Possible security vulnarability because some pgsodium functions still have PUBLIC execute permission
I'm new to pgsodium and we wanted to look if it's functionality can be used for us for e.g. transparant column encrytion to encrypt sensitive data. I'm not a big...