Skip to content

v1.2.0 Release: PG 14 by Default
Compare
Choose a tag to compare
@Vonng Vonng released this 03 Nov 03:13
v1.2.0
55f9937

  • [ENHANCEMENT] Use PostgreSQL 14 as default version

  • [ENHANCEMENT] Use TimescaleDB 2.5 as default extension

    • now timescaledb & postgis are enabled in cmdb by default

  • [ENHANCEMENT] new monitor-only mode:

    • you can use pigsty to monitor existing pg instances with a connectable url only
    • pg_exporter will be deployed on meta node locally
    • new dashboard PGSQL Cluster Monly for remote clusters

  • [ENHANCEMENT] Software upgrade

    • Postgres to 14.0
    • TimescaleDB to 2.5
    • grafana to 8.2.2
    • pev2 to v0.11.9
    • promscale to 0.6.2
    • pgweb to 0.11.9
    • Add new extensions: pglogical pg_stat_monitor orafce

  • [ENHANCEMENT] Automatic detect machine spec and use proper node_tune and pg_conf templates

  • [ENHANCEMENT] Rework on bloat related views, now more information are exposed

  • [ENHANCEMENT] Remove timescale & citus internal monitoring

  • [ENHANCEMENT] New playbook pgsql-audit.yml to create audit report.

  • [BUG FIX] now pgbouncer_exporter resource owner are {{ pg_dbsu }} instead of postgres

  • [BUG FIX] fix pg_exporter duplicate metrics on pg_table pg_index while executing REINDEX TABLE CONCURRENTLY

  • [BUG FIX] fix register_grafana logic: put password in secureJsonData instead of jsonData

  • [BUG FIX] fix cmdb.sql: now pglog.sample can handle different version of postgres csv log

    • pglog.sample is a parent table with three child table sample12, sample13, sample14
    • pglog shortcuts are enhanced into pglog12, pglog13, pglog14 (<- pglog). which will pour csvlog into right table.

  • [CHANGE] now all config templates are minimize into two: auto & demo. (removed: pub4, pg14, demo4, tiny, oltp )

    • pigsty-demo is configured if vagrant is the default user, otherwise pigsty-auto is used.

  • [Application] applog can visualize your Apple iOS15 privacy log.

How to upgrade from v1.1.1

There's no API change in 1.2.0.

You can still use old pigsty.yml configuration files (PG13).

For the infrastructure part. Re-execution of infra.yml will do most of the parts

As for the database. You can still use the existing PG13 instances. In-place upgrade to PG14 is quite
tricky especially when involving extensions such as PostGIS & Timescale. I would highly recommend
performing a database migration with logical replication.

The new playbook pgsql-migration.yml will make this a lot easier. It will create a series of
scripts which will help you to migrate your cluster with near-zero downtime.

Assets 5
Loading