Oleksii Kliukin
Oleksii Kliukin
http://www.postgresql.org/docs/9.5/static/libpq-envars.html I find it rather unsafe to either specify the password from the command-line, or use the environment variable.
When postmaster reinitializes postgres processes because of the crash of one of them, pg_cron is terminated and is not subsequently restarted. The reason is that it supplies the BGW_NEVER_RESTART flag...
Makes those parameters in the operator no-op, see https://github.com/zalando-incubator/postgres-operator/issues/330
On one occasion by looking at the sprocs/all page of pgObserver, I couldn't find the sproc that was actively called on the running database. The reason was, it was older...
During the failover of the database being monitored we observed that PGObserver resets its sp_calls (total number of calls) metrics to 0, confusing our reporting script. This is a bug,...
We had an index that was shown as 0,3 bloat ratio (meaning 0,3%) and 0 bytes to win by the PGObserver estimator, while the estimate at https://github.com/ioguix/pgsql-bloat-estimation/blob/master/btree/btree_bloat.sql shown it as...
Use PG version represented as an integer internally insteead of the float (float comparisons are imprecise). Instead of passing one version of the disk stat collector pass one version per...
For PostgreSQL 9.6, the wait events collect much more types of waits than a heavyweight locks used in the prior versions. We could report them to the user, as well...
Please provide the following information when submitting an issue (feature requests or general comments can skip this): 1. pgBackRest version: `v2.48` 3. PostgreSQL version: It Happens with different PostgreSQL versions,...
Relies on the reporting of those into the maintenance.unresolved2pc by https://github.com/adjust/reshard/pull/7