Ad Widget

Collapse

Zabbix Timescaledb, errors during upgrade to 5.0 with double.sql

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • eithor
    Member
    • May 2020
    • 50

    #1

    Zabbix Timescaledb, errors during upgrade to 5.0 with double.sql

    Hi,

    I've upgraded from Zabbix 4.4 with Timescaledb to Zabbix 5.0. When I try to run the double.sql against the Timescaledb I get the following error:

    Code:
    psql:double.sql:7: ERROR: ONLY option not supported on hypertable operations
    psql:double.sql:10: ERROR: ONLY option not supported on hypertable operations
    How do I modify the double.sql so that it will work with Timescaledb?

    I have Postgresql 11.7 and Timescaledb 1.6 on Debian 10.

    Best,
    Eirik
  • gofree
    Senior Member
    Zabbix Certified SpecialistZabbix Certified Professional
    • Dec 2017
    • 400

    #2
    check the docu for answers

    Comment

    • eithor
      Member
      • May 2020
      • 50

      #3
      Hi,

      It was from that page I found the instruction to run double.sql.
      I re-read the page now, and as far as I can see, there is not any information regarding this error.
      There is only a note that timescaledb compression is not to be turned on until after the double.sql has run (I have compression off), and a note that precision for postgresql 11 is lower.

      I found someone at the Zabbix Russian forum that asked for the same (according to google translate). The suggestion there was to just remove the "only" keyword from the provided double.sql.

      I will try that.

      Best,
      Eirik

      Comment

      • alexswert
        Junior Member
        • May 2020
        • 1

        #4
        Hi,

        I have the same issue after upgrade zabbix 4.4 to 5.0 with posgresl/timescaledb.
        Could you tell me how to set compression off and if removing "Only" keyword is working?
        Thanks,

        Alex

        Comment

        • ik_zelf
          Member
          • Feb 2015
          • 60

          #5
          Removing ONLY works OK. No problems at all. Check https://www.postgresql.org/docs/9.1/....html#AEN62466 for the effects of the ONLY keyword.

          Comment

          Working...