Ad Widget

Collapse

Upgrading TimescaleDB from 1.7.1 to 2.5.0

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • RobertoX
    Junior Member
    • Jul 2020
    • 6

    #1

    Upgrading TimescaleDB from 1.7.1 to 2.5.0

    I have a problem, after upgrading timescale 1.X to 2.X all of zabbix scheduled jobs start to failing.
    Maybe anyone knows where I can find the log file from timescaledb or how to find out what's wrong ??
    I already try to disable and enable compression from zabbix GUI.

    \dx
    List of installed extensions
    Name | Version | Schema | Description
    -------------+---------+------------+-------------------------------------------------------------------
    plpgsql | 1.0 | pg_catalog | PL/pgSQL procedural language
    timescaledb | 2.5.0 | public | Enables scalable inserts and complex queries for time-series data
    SELECT * FROM timescaledb_information.job_stats;
    public | history_log | 1011 | 2021-11-27 16:10:33.432151+01 | -infinity | Failed | Scheduled | 00:00:00.018576 | 2021-11-27 18:08:40.950727+01 | 2 | 0 | 2
    public | history_str | 1009 | 2021-11-27 15:58:27.468091+01 | -infinity | Failed | Scheduled | 00:00:00.272306 | 2021-11-27 16:57:31.490397+01 | 1 | 0 | 1
    public | history_text | 1010 | 2021-11-27 15:58:27.469371+01 | -infinity | Failed | Scheduled | 00:00:00.270849 | 2021-11-27 16:57:31.49022+01 | 1 | 0 | 1
    public | history_uint | 1008 | 2021-11-27 15:58:27.465046+01 | -infinity | Failed | Scheduled | 00:00:00.275198 | 2021-11-27 16:57:31.490244+01 | 1 | 0 | 1
    public | trends | 1012 | 2021-11-27 15:58:27.745545+01 | -infinity | Failed | Scheduled | 00:00:00.018485 | 2021-11-27 16:57:31.51403+01 | 1 | 0 | 1
    public | trends_uint | 1013 | 2021-11-27 15:58:27.419373+01 | -infinity | Failed | Scheduled | 00:00:00.321404 | 2021-11-27 16:57:31.490777+01 | 1 | 0 | 1
    | | 1 | 2021-11-27 02:45:19.624515+01 | 2021-11-27 02:45:20.487438+01 | Success

  • RobertoX
    Junior Member
    • Jul 2020
    • 6

    #2
    This is what I found in postgresql log file
    2021-11-26 18:27:49.913 CET [205649] LOG: job 1006 threw an error
    2021-11-26 18:27:49.913 CET [205649] ERROR: invalid time argument type "bigint"
    2021-11-26 18:27:49.913 CET [205649] HINT: Try casting the argument to "integer".
    2021-11-26 18:27:49.913 CET [205649] CONTEXT: PL/pgSQL function _timescaledb_internal.policy_compression_integer(i nteger,integer,bigint,integer,boolean,boolean) line 17 at FOR over SELECT rows
    SQL statement "CALL _timescaledb_internal.policy_compression_integer(
    job_id, htid, lag_integer,
    maxchunks, verbose_log, recompress_enabled )"
    PL/pgSQL function _timescaledb_internal.policy_compression(integer,j sonb) line 62 at CALL
    2021-11-26 18:27:49.915 CET [988] LOG: background worker "Compression Policy [1006]" (PID 205649) exited with exit code 1

    Comment

    • RobertoX
      Junior Member
      • Jul 2020
      • 6

      #3
      OK! Solved!
      It's TimeScaleDB 2.5.0 Issue. Running command
      alter extension timescaledb update to '2.4.2';
      solved the issue!

      Comment

      Working...