Skip to content

Commit

Permalink
Release 0.49.1
Browse files Browse the repository at this point in the history
  • Loading branch information
lfittl committed Mar 11, 2023
1 parent e5e340f commit c21656c
Show file tree
Hide file tree
Showing 4 changed files with 34 additions and 5 deletions.
29 changes: 29 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,34 @@
# Changelog

## 0.49.1 2023-03-10

* Relation queries: Correctly handle later queries encountering a lock
- This fixes edge cases where relation metadata (e.g. which indexes exist)
can appear and disappear from one snapshot to the next, due to locks
held for parts of the snapshot collection
* Relation statistics: Avoid bogus data due to diffs against locked objects
- This fixes a bug where table or index statistics can be skipped due to
locks held on the relation, and that causing a bad data point to be
collected on a subsequent snapshot, since the prior snapshot would be
missing an entry for that relation. Fixed by consistently skipping
statistics for that table/index in such situations.
* Amazon RDS / Aurora: Support new long-lived CA authorities
- Introduces the new "rds-ca-global" option for db_sslrootcert, which is the
recommended configuration for RDS and Aurora going forward, which encompasses
both "rds-ca-2019-root" and all newer RDS CAs such as "rds-ca-rsa2048-g1".
- For compatibility reasons we still support naming the "rds-ca-2019-root" CA
explicitly, but its now just an alias for the global set.
* Citus: Add option to turn off collection of Citus schema statistics
- For certain Citus deployments, running the relation or index size functions
can fail or time out due to a very high number of distributed tables.
- Adds the new option "disable_citus_schema_stats" / "DISABLE_CITUS_SCHEMA_STATS"
to turn off the collection of these statistics. When using this option its
recommended to instead monitor the workers directly for table and index sizes.
* Add troubleshooting HINT when creating pg_stat_statements extension fails
- This commonly fails due to creating pg_stat_statements on the wrong database,
see https://pganalyze.com/docs/install/troubleshooting/pg_stat_statements


## 0.49.0 2023-02-27

* Update pg_query_go to v4 / Postgres 15 parser
Expand Down
4 changes: 2 additions & 2 deletions contrib/helm/pganalyze-collector/Chart.yaml
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
apiVersion: v2
name: pganalyze-collector
version: 0.49.0
appVersion: "v0.49.0"
version: 0.49.1
appVersion: "v0.49.1"
type: application
description: pganalyze statistics collector
home: https://pganalyze.com/
Expand Down
4 changes: 2 additions & 2 deletions packages/Makefile
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
export NAME=pganalyze-collector
export VERSION=0.49.0
export GIT_VERSION=v0.49.0
export VERSION=0.49.1
export GIT_VERSION=v0.49.1
#export GIT_VERSION=HEAD
#export GIT_VERSION=618e85ce5ed5365bc7d9d9da866fdeb73bac5a55
#export VERSION=$(shell git show -s --format=%ct.%h HEAD)
Expand Down
2 changes: 1 addition & 1 deletion util/version.go
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
package util

const CollectorVersion = "0.49.0"
const CollectorVersion = "0.49.1"
const CollectorNameAndVersion = "pganalyze-collector " + CollectorVersion

0 comments on commit c21656c

Please sign in to comment.