Ad Widget

Collapse

[Z3005] query failed PGRES_FATAL_ERROR:ERROR

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • aks8
    Junior Member
    • Mar 2023
    • 2

    #1

    [Z3005] query failed PGRES_FATAL_ERROR:ERROR

    Здравствуйте!

    Журнал переполняется данными сообщениями:

    Code:
    224:20230322:234143.422 [Z3005] query failed: [0] PGRES_FATAL_ERROR:ERROR: insert into a compressed chunk that has primary or unique constraint is not supported
    [insert into trends_uint (itemid,clock,num,value_min,value_avg,value_max) values (47503,1679511600,1,1678709646,1678709646,16787096 46);
    ]
    225:20230322:234224.479 [Z3005] query failed: [0] PGRES_FATAL_ERROR:ERROR: insert into a compressed chunk that has primary or unique constraint is not supported
    [insert into trends_uint (itemid,clock,num,value_min,value_avg,value_max) values (44844,1679511600,1,1676151544,1676151544,16761515 44);
    ]
    225:20230322:234251.516 [Z3005] query failed: [0] PGRES_FATAL_ERROR:ERROR: insert into a compressed chunk that has primary or unique constraint is not supported
    [insert into trends_uint (itemid,clock,num,value_min,value_avg,value_max) values (47570,1679511600,1,1678709593,1678709593,16787095 93);
    ]
    225:20230322:234358.606 [Z3005] query failed: [0] PGRES_FATAL_ERROR:ERROR: insert into a compressed chunk that has primary or unique constraint is not supported
    [insert into trends_uint (itemid,clock,num,value_min,value_avg,value_max) values (47637,1679511600,1,1678709681,1678709681,16787096 81);
    ]
    224:20230322:234516.703 [Z3005] query failed: [0] PGRES_FATAL_ERROR:ERROR: insert into a compressed chunk that has primary or unique constraint is not supported
    [insert into trends_uint (itemid,clock,num,value_min,value_avg,value_max) values (45016,1679511600,1,1678709652,1678709652,16787096 52);
    
    ...
    
    
    ​
    Zabbix 6.0.14 + PgSQL 14 + TimeScale 2.8.1


    Как можно исправить?

  • Kos
    Senior Member
    Zabbix Certified SpecialistZabbix Certified Professional
    • Aug 2015
    • 3404

    #2
    Смутно помнится, что были какие-то ограничения на использование компрессии в TimeScale DB.
    Проверьте, пожалуйста, всё, что описано на этой странице (ссылка), особенно в последнем разделе (TimescaleDB compression).

    Comment

    • aks8
      Junior Member
      • Mar 2023
      • 2

      #3
      Статью просмотрел, вроде бы не нашел каких то противоречий с моими настройками.
      Attached Files

      Comment

      Working...