Re: sequence id overflow ERROR using timescaledb

From: Julien Rouhaud <rjuju123(at)gmail(dot)com>
To: abrahim abrahao <abrahimsabrahao(at)yahoo(dot)ca>
Cc: "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: sequence id overflow ERROR using timescaledb
Date: 2022-08-05 02:37:39
Message-ID: 20220805023739.r7hgrcgpz4lgxsyz@jrouhaud
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hi,

On Thu, Aug 04, 2022 at 08:47:16PM +0000, abrahim abrahao wrote:
>
>  I am using timescaledb version  2.7.2, and PostgreSQL 12.11
> [...]
> I tried to compress a chuck using the compress_chunk function and running a
> job as well, and I got "sequence id overflow" message ERROR.Any idea how to
> fix it or why I got this error?Note: I compressed other chuckles without
> problem.
> [...]
>    SELECT  'set temp_file_limit =-1; SELECT compress_chunk(''' || chunk_schema|| '.' || chunk_name || ''');'  
> [...]
> ERROR:  sequence id overflow
> CONTEXT:  SQL statement "SELECT public.compress_chunk( chunk_rec.oid )"
> PL/pgSQL function _timescaledb_internal.policy_compression_execute(integer,integer,anyelement,integer,boolean,boolean) line 35 at PERFORM
> SQL statement "CALL _timescaledb_internal.policy_compression_execute(
>         job_id, htid, lag_value::INTERVAL,
>         maxchunks, verbose_log, recompress_enabled
>       )"
> PL/pgSQL function _timescaledb_internal.policy_compression(integer,jsonb) line 51 at CALL
> Time: 1113429.153 ms (18:33.429)

This error is coming from timescale, not postgres, so you should open an issue
on their repository instead.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Peter Smith 2022-08-05 06:03:29 Re: Support logical replication of DDLs
Previous Message Jan Wieck 2022-08-04 23:57:22 Re: Purpose of DEFERRABLE _and_ INITIALLY DEFERRED foreign key constraint checking?