Ad Widget

Collapse

added timescale to postgres and getting errors

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • william-cl
    Junior Member
    • May 2023
    • 16

    #1

    added timescale to postgres and getting errors

    our environment 6.4 with postgresql 14 will not start now due to the below as an example. But there are over a thousand duplicates.

    4 [Z3008] query failed due to primary key constraint: [0] PGRES_FATAL_ERROR:ERROR: duplicate key value violates unique constraint "4056_2343_history_pkey"
    DETAIL: Key (itemid, clock, ns)=(138435, 1735227195, 920212859) already exists.

    any and all help is greatly appreciated.
    Last edited by william-cl; 26-12-2024, 17:42.
  • Blevar
    Member
    • Jan 2025
    • 68

    #2
    This looks like duplicate keys are trying to use primary key - which is constrained in your db. Backup your db and then try identifying and removing duplicated items.

    Comment

    Working...