Search results

"aggressive" vacuum mode should be something like "wraparound" instead

Status: Open.

#28 In TritonDataCenter/pgstatsmon;

· chudley opened on Jul 31, 2019

Could expose some/all of pg_settings

Status: Open.

#27 In TritonDataCenter/pgstatsmon;

· chudley opened on May 21, 2019

Negative byte lag calculated from pgstatsmon metrics after shard rebuild

Status: Open.

#23 In TritonDataCenter/pgstatsmon;

· luke-jarymowycz opened on Dec 13, 2018

Stale metrics reported after shard changes state

Status: Open.

#22 In TritonDataCenter/pgstatsmon;

· luke-jarymowycz opened on Dec 13, 2018

allow tunable superuser for pgstatsmon setup routines

Status: Open.

#21 In TritonDataCenter/pgstatsmon;

· KodyKantor opened on Sep 13, 2018

could provide more metrics about pgstatsmon

Status: Open.

#19 In TritonDataCenter/pgstatsmon;

· KodyKantor opened on Sep 5, 2018

Use different schema for pgstatsmon-specific functions and types

Status: Open.

#16 In TritonDataCenter/pgstatsmon;

· kellymclaughlin opened on Jul 23, 2018

collect lock stats

Status: Open.

#15 In TritonDataCenter/pgstatsmon;

· KodyKantor opened on Jun 28, 2018

could use VMAPI changefeed instead of polling for backend discovery

Status: Open.

#9 In TritonDataCenter/pgstatsmon;

· KodyKantor opened on May 2, 2018

could protect against data modification

Status: Open.

#6 In TritonDataCenter/pgstatsmon;

· KodyKantor opened on Apr 5, 2018