Uploaded image for project: 'ZABBIX BUGS AND ISSUES'
  1. ZABBIX BUGS AND ISSUES
  2. ZBX-26744

Compression policy log messages after upgrade to 7.2.11 and TSDB 2.20

XMLWordPrintable

    • Icon: Problem report Problem report
    • Resolution: Duplicate
    • Icon: Trivial Trivial
    • None
    • 7.2.11
    • None
    • None

      Hello Team,

      As in the title, after the Zabbix startup there are following log messages after upgrading from 7.2.10 to 7.2.11 and TSDB from 2.19.X to 2.20.X

      1691698:20250722:140445.766 [Z3005] query failed: [0] PGRES_FATAL_ERROR:ERROR:  columnstore policy already exists for hypertable or continuous aggregate "history_uint"
      HINT:  Set option "if_not_exists" to true to avoid error.
       [select add_compression_policy('history_uint', integer '612000')]
      1691698:20250722:140445.766 failed to add compression policy to table 'history_uint'
      1691698:20250722:140445.771 [Z3005] query failed: [0] PGRES_FATAL_ERROR:ERROR:  columnstore policy already exists for hypertable or continuous aggregate "history_str"
      HINT:  Set option "if_not_exists" to true to avoid error.
       [select add_compression_policy('history_str', integer '612000')]
      1691698:20250722:140445.772 failed to add compression policy to table 'history_str'
      1691705:20250722:140445.776 thread started [discovery worker #1]
      1691851:20250722:140445.777 server #143 started [icmp pinger #12]
      1691878:20250722:140445.778 thread started
      1691698:20250722:140445.779 [Z3005] query failed: [0] PGRES_FATAL_ERROR:ERROR:  columnstore policy already exists for hypertable or continuous aggregate "history_text"
      HINT:  Set option "if_not_exists" to true to avoid error.
       [select add_compression_policy('history_text', integer '612000')]
      1691698:20250722:140445.779 failed to add compression policy to table 'history_text'
      1691698:20250722:140445.783 [Z3005] query failed: [0] PGRES_FATAL_ERROR:ERROR:  columnstore policy already exists for hypertable or continuous aggregate "history_log"
      HINT:  Set option "if_not_exists" to true to avoid error.
       [select add_compression_policy('history_log', integer '612000')]
      1691698:20250722:140445.783 failed to add compression policy to table 'history_log'
      1691698:20250722:140445.788 [Z3005] query failed: [0] PGRES_FATAL_ERROR:ERROR:  columnstore policy already exists for hypertable or continuous aggregate "history_bin"
      HINT:  Set option "if_not_exists" to true to avoid error.
       [select add_compression_policy('history_bin', integer '612000')]
      1691698:20250722:140445.788 failed to add compression policy to table 'history_bin'
      1691698:20250722:140445.795 [Z3005] query failed: [0] PGRES_FATAL_ERROR:ERROR:  columnstore policy already exists for hypertable or continuous aggregate "trends"
      HINT:  Set option "if_not_exists" to true to avoid error.
       [select add_compression_policy('trends', integer '612000')]
      1691698:20250722:140445.795 failed to add compression policy to table 'trends'
      1691698:20250722:140445.802 [Z3005] query failed: [0] PGRES_FATAL_ERROR:ERROR:  columnstore policy already exists for hypertable or continuous aggregate "trends_uint"
      HINT:  Set option "if_not_exists" to true to avoid error.
       [select add_compression_policy('trends_uint', integer '612000')]
      1691698:20250722:140445.802 failed to add compression policy to table 'trends_uint'
      1691698:20250722:140445.805 [Z3005] query failed: [0] PGRES_FATAL_ERROR:ERROR:  columnstore policy already exists for hypertable or continuous aggregate "auditlog"
      HINT:  Set option "if_not_exists" to true to avoid error.
       [select add_compression_policy('auditlog', compress_created_before => interval '612000')]
      1691698:20250722:140445.805 failed to add compression policy to table 'auditlog'
      

            zabbix.dev Zabbix Development Team
            azyla Arkadiusz Zyla (Inactive)
            Votes:
            1 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: