Comments (17)
hostops
commented on June 2, 2024
I also believe this is linked to this issue: #6031
from timescaledb.
antekresic
commented on June 2, 2024
Hi there,
Could you send us the schema definitions of the hypertable and also your compression settings? It does look like the DELETE is the problem here.
Thanks,
from timescaledb.
hostops
commented on June 2, 2024
Table "public.signal"
Column | Type | Collation | Nullable | Default
--------+-----------------------------+-----------+----------+---------
id | bigint | | not null |
time | timestamp without time zone | | not null |
value | double precision | | |
Indexes:
"signal_id_time_idx" btree (id, "time" DESC)
"signal_time_idx" btree ("time" DESC)
Triggers:
ts_insert_blocker BEFORE INSERT ON signal FOR EACH ROW EXECUTE FUNCTION _timescaledb_functions.insert_blocker()
Number of child tables: 362 (Use \d+ to list them.)
Table "public.aggregated"
Column | Type | Collation | Nullable | Default
--------------+-----------------------------+-----------+----------+---------
id | bigint | | not null |
time | timestamp without time zone | | not null |
duration | double precision | | not null |
integral | double precision | | not null |
rising_edges | integer | | not null |
min | double precision | | |
max | double precision | | |
level | aggregation_level | | not null |
Indexes:
"aggregated_id_level_time_idx" btree (id, level, "time" DESC)
"aggregated_time_idx" btree ("time" DESC)
Triggers:
ts_insert_blocker BEFORE INSERT ON aggregated FOR EACH ROW EXECUTE FUNCTION _timescaledb_functions.insert_blocker()
Number of child tables: 361 (Use \d+ to list them.)
CREATE TABLE signal (
id BIGINT NOT NULL,
time TIMESTAMP NOT NULL,
value DOUBLE PRECISION NULL
);
SELECT create_hypertable('signal', 'time', chunk_time_interval => interval '10 days');
CREATE TABLE aggregated (
id BIGINT NOT NULL,
time TIMESTAMP NOT NULL,
duration DOUBLE PRECISION NOT NULL,
integral DOUBLE PRECISION NOT NULL,
rising_edges INT NOT NULL,
min DOUBLE PRECISION NULL,
max DOUBLE PRECISION NULL,
UNIQUE (time, id)
);
SELECT create_hypertable('aggregated', 'time', chunk_time_interval => interval '10 days');
To compress data we use Kubernetes cronjob, and we run queries below once a week:
SELECT compress_chunk(CONCAT(chunk_schema, '.', chunk_name)::regclass, if_not_compressed => true)
FROM timescaledb_information.chunks
WHERE
hypertable_name IN ('signal','aggregated')
AND range_end < NOW()-INTERVAL '91 days' ;
VACUUM ANALYZE;
from timescaledb.
mkindahl
commented on June 2, 2024
This seems like it could be related to #6717, which would make COPY the problem.
A workaround for this would be to use INSERT instead of COPY or decompress the chunks before running COPY.
The fix above is not released yet, but it is very likely to be in the next release.
Could you show me the part of the code that involves the DELETE and the COPY? We have a reproduction using COPY already, but it would be good if we could rule out that the DELETE is the problem.
from timescaledb.
hostops
commented on June 2, 2024
There is too much code to share the whole code. So I extracted only relevant SQL.
For each data upload, we run these queries:
DELETE FROM signal WHERE id = $1 AND time >= $2 AND time < $3;
COPY signal (id, time, value) FROM STDIN BINARY;
INSERT INTO signal VALUES ($id, $time, NULL) ON CONFLICT DO NOTHING;
from timescaledb.
mkindahl
commented on June 2, 2024
@hostops I tried to reproduce it in different ways but have not yet succeeded. Can you get access to the stack trace for the crash or show more in the log about what caused the crash?
The log extract you showed above just shows that the delete statement cannot be executed because the server is in recovery mode, not what statement caused the crash.
Here is an example of something I did:
postgres=# \dx
List of installed extensions
-[ RECORD 1 ]--------------------------------------------------------------------------------------
Name | plpgsql
Version | 1.0
Schema | pg_catalog
Description | PL/pgSQL procedural language
-[ RECORD 2 ]--------------------------------------------------------------------------------------
Name | timescaledb
Version | 2.14.2
Schema | public
Description | Enables scalable inserts and complex queries for time-series data (Community Edition)
postgres=# \d signal
Table "public.signal"
Column | Type | Collation | Nullable | Default
--------+-----------------------------+-----------+----------+---------
id | bigint | | not null |
time | timestamp without time zone | | not null |
value | double precision | | |
Indexes:
"signal_time_idx" btree ("time" DESC)
Triggers:
ts_insert_blocker BEFORE INSERT ON signal FOR EACH ROW EXECUTE FUNCTION _timescaledb_functions.insert_blocker()
Number of child tables: 1 (Use \d+ to list them.)
postgres=# \copy _timescaledb_internal._hyper_1_1_chunk (id, time, value) to 'magic.dat' binary
COPY 10
postgres=# select * from signal;
id | time | value
----+---------------------------+-------
12 | 2024-01-20 15:02:03.87313 | 3.14
13 | 2024-01-20 15:02:03.87313 | 2.14
12 | 2024-01-20 15:02:03.87313 | 3.14
13 | 2024-01-20 15:02:03.87313 | 2.14
12 | 2024-01-20 15:02:03.87313 | 3.14
13 | 2024-01-20 15:02:03.87313 | 2.14
12 | 2024-01-20 15:02:03.87313 | 3.14
13 | 2024-01-20 15:02:03.87313 | 2.14
12 | 2024-01-20 15:02:03.87313 | 3.14
13 | 2024-01-20 15:02:03.87313 | 2.14
(10 rows)
postgres=# DELETE FROM signal WHERE id = 12 AND time >= '2024-01-20 00:00:00Z' AND time < '2024-01-21 00:00:00Z';
DELETE 5
postgres=# \copy signal(id,time,value) from 'magic.dat' binary
COPY 10
from timescaledb.
hostops
commented on June 2, 2024
Hello! I did not know I missed the important part of the logs:
2024-03-08 11:28:52 LOG: server process (PID 395739) was terminated by signal 11: Segmentation fault
2024-03-08 11:28:52 DETAIL: Failed process was running: DELETE FROM signal WHERE id = $1 AND time >= $2 AND time < $3;
2024-03-08 11:28:52 LOG: terminating any other active server processes
2024-03-08 11:28:52 FATAL: could not receive data from WAL stream: server closed the connection unexpectedly
2024-03-08 11:28:52 This probably means the server terminated abnormally
2024-03-08 11:28:52 before or while processing the request.
2024-03-08 11:28:52 LOG: record with incorrect prev-link 0/DC at 8FDD/416319B0
2024-03-08 11:28:59 2024-03-08 10:28:59,394 INFO: closed patroni heartbeat connection to postgres
2024-03-08 10:29:00 INFO: establishing a new patroni heartbeat connection to postgres
2024-03-08 11:29:12 LOG: server process (PID 397119) was terminated by signal 11: Segmentation fault
2024-03-08 11:29:12 DETAIL: Failed process was running: DELETE FROM signal WHERE id = $1 AND time >= $2 AND time < $3;
2024-03-08 11:29:12 LOG: terminating any other active server processes
2024-03-08 11:29:12 FATAL: could not receive data from WAL stream: server closed the connection unexpectedly
2024-03-08 11:29:12 This probably means the server terminated abnormally
2024-03-08 11:29:12 before or while processing the request.
2024-03-08 11:29:12 LOG: unexpected pageaddr 8FDD/2A64C000 in log segment 0000004200008FDD00000041, offset 6602752
2024-03-08 11:29:12 [unknown] FATAL: the database system is in recovery mode
from timescaledb.
hostops
commented on June 2, 2024
I also tried the same test in our development environment as you @mkindahl, but I can only get it to fail in production.
Here is the relevant code:
async fn do_save(db: &PostgresService, signal: &Signal) -> Result<(), DatabaseError> {
let mut client = log_slow(
db.get_conn(&crate::prometheus::CONN_SIGNAL_SAVE),
"signal_repo, pool.get()",
5,
)
.await?;
let transaction = log_slow(
client
.build_transaction()
.isolation_level(Serializable)
.start(),
"signal_repo, transaction.start()",
5,
)
.await?;
log_slow(
clear_period(&transaction, signal),
"signal_repo, clear_period",
5,
)
.await?;
insert(&transaction, signal.id.into(), &signal.points)
.timed(&crate::prometheus::TIME_SIG_INSERT)
.await?;
log_slow(transaction.commit(), "signal_repo, transaction.commit()", 5).await?;
Ok(())
}
async fn insert(
transaction: &Transaction<'_>,
id: i64,
points: &[DataPoint],
) -> Result<(), DatabaseError> {
// open COPY FROM STDIN sink
let sink = transaction
.copy_in("COPY signal (id, time, value) FROM STDIN BINARY")
.await?;
let writer = BinaryCopyInWriter::new(sink, &[Type::INT8, Type::TIMESTAMP, Type::FLOAT8]);
pin_mut!(writer);
// write all points except last
for p in &points[0..points.len() - 1] {
if let Some(value) = p.value {
writer
.as_mut()
.write(&[&id, &wrap_time(p.timestamp), &value])
.await?;
} else {
writer
.as_mut()
.write(&[&id, &wrap_time(p.timestamp), &None::<&f64>])
.await?;
}
}
writer.finish().await?;
// insert last point with INSERT to utilise ON CONFLICT
// because we clear before inserting, conflict may arise only for last data point
// since last data point is always null, on conflict we want to preserve current value
let last_timestamp = (points.last().unwrap().timestamp as f64) / 1000.0;
let last_insert = format!(
"INSERT INTO signal VALUES ({:}, to_timestamp({:0.3}), NULL) ON CONFLICT DO NOTHING;",
id, last_timestamp
);
transaction.simple_query(&last_insert[..]).await?;
Ok(())
}from timescaledb.
mkindahl
commented on June 2, 2024
@hostops Definitely delete failing then, so #6717 will not solve this issue. If you have a stack trace that would help a lot since it is hard to figure out where in the code it is failing.
from timescaledb.
KamalAman
commented on June 2, 2024
This might be related to #6028 and or #6031, i just updated to 2.14 and it cleared a similar issue out
from timescaledb.
hostops
commented on June 2, 2024
I just tested simple delete query in compressed chunk and bug was reproduced.
DELETE FROM signal WHERE id=738744145666 AND "time" BETWEEN '2023-10-01' AND '2023-11-02';
LOG: server process (PID 45855) was terminated by signal 11: Segmentation fault
DETAIL: Failed process was running: DELETE FROM signal WHERE id=738744145666 AND "time" BETWEEN '2023-10-01' AND '2023-11-02';
from timescaledb.
mkindahl
commented on June 2, 2024
I just tested simple delete query in compressed chunk and bug was reproduced.
DELETE FROM signal WHERE id=738744145666 AND "time" BETWEEN '2023-10-01' AND '2023-11-02';LOG: server process (PID 45855) was terminated by signal 11: Segmentation fault DETAIL: Failed process was running: DELETE FROM signal WHERE id=738744145666 AND "time" BETWEEN '2023-10-01' AND '2023-11-02';
Do you have a stack trace for this?
from timescaledb.
hostops
commented on June 2, 2024
If you mean stack trace on client. I just executed this command using psql.
If log_min_messages=DEBUG5
and log_min_error_statement=DEBUG5 would be enough for server, I can get it. But if you mean I should get stack trace using gdb it would take me more time.
from timescaledb.
mkindahl
commented on June 2, 2024
If you mean stack trace on client. I just executed this command using
psql.If
log_min_messages=DEBUG5andlog_min_error_statement=DEBUG5would be enough for server, I can get it. But if you mean I should get stack trace usinggdbit would take me more time.
I meant a stack trace using gdb. It would help us to verify if this is a bug we've seen previously and possibly fix it if it is not. I'll try again to see if I can reproduce it.
from timescaledb.
hostops
commented on June 2, 2024
@mkindahl I believe this is the stack trace you are looking for.
Already logging to /var/lib/postgresql/data/debuglog.txt.
Attaching to process 172
Reading symbols from /usr/lib/postgresql/15/bin/postgres...
Reading symbols from /usr/lib/debug/.build-id/a1/7fec33e3a8cf89bd57230032466c94be408f6f.debug...
Reading symbols from /lib/x86_64-linux-gnu/libzstd.so.1...
(No debugging symbols found in /lib/x86_64-linux-gnu/libzstd.so.1)
Reading symbols from /lib/x86_64-linux-gnu/liblz4.so.1...
(No debugging symbols found in /lib/x86_64-linux-gnu/liblz4.so.1)
Reading symbols from /lib/x86_64-linux-gnu/libxml2.so.2...
(No debugging symbols found in /lib/x86_64-linux-gnu/libxml2.so.2)
Reading symbols from /lib/x86_64-linux-gnu/libpam.so.0...
(No debugging symbols found in /lib/x86_64-linux-gnu/libpam.so.0)
Reading symbols from /lib/x86_64-linux-gnu/libssl.so.3...
(No debugging symbols found in /lib/x86_64-linux-gnu/libssl.so.3)
Reading symbols from /lib/x86_64-linux-gnu/libcrypto.so.3...
(No debugging symbols found in /lib/x86_64-linux-gnu/libcrypto.so.3)
Reading symbols from /lib/x86_64-linux-gnu/libgssapi_krb5.so.2...
(No debugging symbols found in /lib/x86_64-linux-gnu/libgssapi_krb5.so.2)
Reading symbols from /lib/x86_64-linux-gnu/libz.so.1...
(No debugging symbols found in /lib/x86_64-linux-gnu/libz.so.1)
Reading symbols from /lib/x86_64-linux-gnu/libm.so.6...
(No debugging symbols found in /lib/x86_64-linux-gnu/libm.so.6)
Reading symbols from /lib/x86_64-linux-gnu/libldap-2.5.so.0...
(No debugging symbols found in /lib/x86_64-linux-gnu/libldap-2.5.so.0)
Reading symbols from /lib/x86_64-linux-gnu/libicui18n.so.70...
(No debugging symbols found in /lib/x86_64-linux-gnu/libicui18n.so.70)
Reading symbols from /lib/x86_64-linux-gnu/libicuuc.so.70...
(No debugging symbols found in /lib/x86_64-linux-gnu/libicuuc.so.70)
Reading symbols from /lib/x86_64-linux-gnu/libsystemd.so.0...
(No debugging symbols found in /lib/x86_64-linux-gnu/libsystemd.so.0)
Reading symbols from /lib/x86_64-linux-gnu/libc.so.6...
(No debugging symbols found in /lib/x86_64-linux-gnu/libc.so.6)
Reading symbols from /lib/x86_64-linux-gnu/liblzma.so.5...
(No debugging symbols found in /lib/x86_64-linux-gnu/liblzma.so.5)
Reading symbols from /lib/x86_64-linux-gnu/libaudit.so.1...
(No debugging symbols found in /lib/x86_64-linux-gnu/libaudit.so.1)
Reading symbols from /lib/x86_64-linux-gnu/libkrb5.so.3...
(No debugging symbols found in /lib/x86_64-linux-gnu/libkrb5.so.3)
Reading symbols from /lib/x86_64-linux-gnu/libk5crypto.so.3...
(No debugging symbols found in /lib/x86_64-linux-gnu/libk5crypto.so.3)
Reading symbols from /lib/x86_64-linux-gnu/libcom_err.so.2...
(No debugging symbols found in /lib/x86_64-linux-gnu/libcom_err.so.2)
Reading symbols from /lib/x86_64-linux-gnu/libkrb5support.so.0...
(No debugging symbols found in /lib/x86_64-linux-gnu/libkrb5support.so.0)
Reading symbols from /lib64/ld-linux-x86-64.so.2...
(No debugging symbols found in /lib64/ld-linux-x86-64.so.2)
Reading symbols from /lib/x86_64-linux-gnu/liblber-2.5.so.0...
(No debugging symbols found in /lib/x86_64-linux-gnu/liblber-2.5.so.0)
Reading symbols from /lib/x86_64-linux-gnu/libsasl2.so.2...
(No debugging symbols found in /lib/x86_64-linux-gnu/libsasl2.so.2)
Reading symbols from /lib/x86_64-linux-gnu/libgnutls.so.30...
(No debugging symbols found in /lib/x86_64-linux-gnu/libgnutls.so.30)
Reading symbols from /lib/x86_64-linux-gnu/libstdc++.so.6...
(No debugging symbols found in /lib/x86_64-linux-gnu/libstdc++.so.6)
Reading symbols from /lib/x86_64-linux-gnu/libgcc_s.so.1...
(No debugging symbols found in /lib/x86_64-linux-gnu/libgcc_s.so.1)
Reading symbols from /lib/x86_64-linux-gnu/libicudata.so.70...
(No debugging symbols found in /lib/x86_64-linux-gnu/libicudata.so.70)
Reading symbols from /lib/x86_64-linux-gnu/libcap.so.2...
(No debugging symbols found in /lib/x86_64-linux-gnu/libcap.so.2)
Reading symbols from /lib/x86_64-linux-gnu/libgcrypt.so.20...
(No debugging symbols found in /lib/x86_64-linux-gnu/libgcrypt.so.20)
Reading symbols from /lib/x86_64-linux-gnu/libcap-ng.so.0...
(No debugging symbols found in /lib/x86_64-linux-gnu/libcap-ng.so.0)
Reading symbols from /lib/x86_64-linux-gnu/libkeyutils.so.1...
(No debugging symbols found in /lib/x86_64-linux-gnu/libkeyutils.so.1)
Reading symbols from /lib/x86_64-linux-gnu/libresolv.so.2...
(No debugging symbols found in /lib/x86_64-linux-gnu/libresolv.so.2)
Reading symbols from /lib/x86_64-linux-gnu/libp11-kit.so.0...
(No debugging symbols found in /lib/x86_64-linux-gnu/libp11-kit.so.0)
Reading symbols from /lib/x86_64-linux-gnu/libidn2.so.0...
(No debugging symbols found in /lib/x86_64-linux-gnu/libidn2.so.0)
Reading symbols from /lib/x86_64-linux-gnu/libunistring.so.2...
(No debugging symbols found in /lib/x86_64-linux-gnu/libunistring.so.2)
Reading symbols from /lib/x86_64-linux-gnu/libtasn1.so.6...
(No debugging symbols found in /lib/x86_64-linux-gnu/libtasn1.so.6)
Reading symbols from /lib/x86_64-linux-gnu/libnettle.so.8...
(No debugging symbols found in /lib/x86_64-linux-gnu/libnettle.so.8)
Reading symbols from /lib/x86_64-linux-gnu/libhogweed.so.6...
(No debugging symbols found in /lib/x86_64-linux-gnu/libhogweed.so.6)
Reading symbols from /lib/x86_64-linux-gnu/libgmp.so.10...
(No debugging symbols found in /lib/x86_64-linux-gnu/libgmp.so.10)
Reading symbols from /lib/x86_64-linux-gnu/libgpg-error.so.0...
(No debugging symbols found in /lib/x86_64-linux-gnu/libgpg-error.so.0)
Reading symbols from /lib/x86_64-linux-gnu/libffi.so.8...
(No debugging symbols found in /lib/x86_64-linux-gnu/libffi.so.8)
Reading symbols from /usr/lib/postgresql/15/lib/timescaledb.so...
Reading symbols from /usr/lib/postgresql/15/lib/pg_stat_statements.so...
Reading symbols from /usr/lib/debug/.build-id/6c/2a36e82a982dde945f9b2fd12f24bbcd30790d.debug...
Reading symbols from /usr/lib/postgresql/15/lib/timescaledb-2.14.0.so...
Reading symbols from /usr/lib/postgresql/15/lib/timescaledb-tsl-2.14.0.so...
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
0x00007ff247c5edea in epoll_wait () from /lib/x86_64-linux-gnu/libc.so.6
Ambiguous command "con": condition, continue.
Continuing.
Program received signal SIGINT, Interrupt.
0x00007ff247c5edea in epoll_wait () from /lib/x86_64-linux-gnu/libc.so.6
Breakpoint 1 at 0x56283cd948b0: file utils/error/./build/../src/backend/utils/error/elog.c, line 509.
Continuing.
Program received signal SIGSEGV, Segmentation fault.
0x00007ff1edc691b4 in fill_predicate_context (is_null=<synthetic pointer>, index_filters=<synthetic pointer>, heap_filters=<synthetic pointer>, predicates=0x0, settings=<optimized out>, ch=<optimized out>) at /build/timescaledb/tsl/src/compression/compression.c:2553
2553 /build/timescaledb/tsl/src/compression/compression.c: No such file or directory.
#0 0x00007ff1edc691b4 in fill_predicate_context (is_null=<synthetic pointer>, index_filters=<synthetic pointer>, heap_filters=<synthetic pointer>, predicates=0x0, settings=<optimized out>, ch=<optimized out>) at /build/timescaledb/tsl/src/compression/compression.c:2553
#1 decompress_batches_for_update_delete.constprop.0 (ht_state=<optimized out>, chunk=chunk@entry=0x56283eb99608, predicates=predicates@entry=0x56283eb990d8, estate=<optimized out>) at /build/timescaledb/tsl/src/compression/compression.c:3065
#2 0x00007ff1edc4133c in decompress_chunk_walker (ps=0x56283eb8a198, ctx=0x7fff3579ff90) at /build/timescaledb/tsl/src/compression/compression.c:3227
#3 0x000056283cb011cc in planstate_walk_members (context=0x7fff3579ff90, walker=0x7ff1edc411f0 <decompress_chunk_walker>, nplans=<optimized out>, planstates=<optimized out>) at nodes/./build/../src/backend/nodes/nodeFuncs.c:4202
#4 planstate_tree_walker (planstate=0x56283eb8d6c8, walker=0x7ff1edc411f0 <decompress_chunk_walker>, context=0x7fff3579ff90) at nodes/./build/../src/backend/nodes/nodeFuncs.c:4124
#5 0x000056283cb01159 in planstate_tree_walker (planstate=0x56283eb89b78, walker=0x7ff1edc411f0 <decompress_chunk_walker>, context=0x7fff3579ff90) at nodes/./build/../src/backend/nodes/nodeFuncs.c:4109
#6 0x00007ff1edc413c6 in decompress_target_segments (ht_state=<optimized out>) at /build/timescaledb/tsl/src/compression/compression.c:3161
#7 0x00007ff1edcecd4d in ExecModifyTable (pstate=0x56283eb89b78, cs_node=0x56283eb896b8) at /build/timescaledb/src/nodes/hypertable_modify.c:752
#8 hypertable_modify_exec (node=0x56283eb896b8) at /build/timescaledb/src/nodes/hypertable_modify.c:181
#9 0x000056283ca8946d in ExecProcNode (node=0x56283eb896b8) at executor/./build/../src/include/executor/executor.h:262
#10 ExecutePlan (execute_once=<optimized out>, dest=0x7ff1ed097880, direction=<optimized out>, numberTuples=0, sendTuples=<optimized out>, operation=CMD_DELETE, use_parallel_mode=<optimized out>, planstate=0x56283eb896b8, estate=0x56283eb88468) at executor/./build/../src/backend/executor/execMain.c:1636
#11 standard_ExecutorRun (queryDesc=0x56283eb872d8, direction=<optimized out>, count=0, execute_once=<optimized out>) at executor/./build/../src/backend/executor/execMain.c:363
#12 0x00007ff245013f75 in pgss_ExecutorRun (queryDesc=0x56283eb872d8, direction=ForwardScanDirection, count=0, execute_once=<optimized out>) at ./build/../contrib/pg_stat_statements/pg_stat_statements.c:1010
#13 0x000056283cc32523 in ExecutorRun (execute_once=true, count=0, direction=ForwardScanDirection, queryDesc=0x56283eb872d8) at executor/./build/../src/backend/executor/execMain.c:305
#14 ProcessQuery (plan=plan@entry=0x7ff1ed097910, sourceText=<optimized out>, params=<optimized out>, queryEnv=<optimized out>, dest=dest@entry=0x7ff1ed097880, qc=qc@entry=0x7fff357a04d0) at tcop/./build/../src/backend/tcop/pquery.c:160
#15 0x000056283cc34142 in PortalRunMulti (portal=portal@entry=0x56283e8910b8, isTopLevel=isTopLevel@entry=true, setHoldSnapshot=setHoldSnapshot@entry=false, dest=dest@entry=0x7ff1ed097880, altdest=altdest@entry=0x7ff1ed097880, qc=qc@entry=0x7fff357a04d0) at tcop/./build/../src/backend/tcop/pquery.c:1277
#16 0x000056283cc346ac in PortalRun (portal=0x56283e8910b8, count=9223372036854775807, isTopLevel=<optimized out>, run_once=<optimized out>, dest=0x7ff1ed097880, altdest=0x7ff1ed097880, qc=0x7fff357a04d0) at tcop/./build/../src/backend/tcop/pquery.c:791
#17 0x000056283cc35403 in exec_simple_query (query_string=0x56283e8184a8 "DELETE FROM signal WHERE id=738744145666 AND \"time\" BETWEEN '2023-10-01' AND '2023-11-02';") at tcop/./build/../src/backend/tcop/postgres.c:1250
#18 0x000056283cc36fb5 in PostgresMain (dbname=<optimized out>, username=<optimized out>) at tcop/./build/../src/backend/tcop/postgres.c:4598
#19 0x000056283cbaa185 in BackendRun (port=0x56283e841b30, port=0x56283e841b30) at postmaster/./build/../src/backend/postmaster/postmaster.c:4514
#20 BackendStartup (port=0x56283e841b30) at postmaster/./build/../src/backend/postmaster/postmaster.c:4242
#21 ServerLoop () at postmaster/./build/../src/backend/postmaster/postmaster.c:1809
#22 0x000056283cb9f196 in PostmasterMain (argc=17, argv=<optimized out>) at postmaster/./build/../src/backend/postmaster/postmaster.c:1481
#23 0x000056283c89ff3b in main (argc=17, argv=0x56283e7832d0) at main/./build/../src/backend/main/main.c:202
Continuing.
Program terminated with signal SIGSEGV, Segmentation fault.
The program no longer exists.
No stack.
from timescaledb.
hostops
commented on June 2, 2024
To save you some time:
timescaledb/tsl/src/compression/compression.c
Line 2553 in 402c1c3
from timescaledb.
mkindahl
commented on June 2, 2024
@hostops Yes, that is what I was looking for. Thanks!
from timescaledb.
Related Issues (20)
- [Bug]: BEFORE INSERT trigger on partitioning columns does not work
- [Bug]: Install Timescaledb for windows on version 2.14.2 failed, but it is successful on version 2.13.1 HOT 4
- PostgreSQL major version upgrades using Docker HOT 5
- [Feature]: Allow chunk size to be based on time or chunk total size of storage
- Constify `cagg_watermark` not working using window functions when querying a CAgg HOT 5
- Timescale DB causes issues with Auto vacuum and Locks up Postgres database causing it to crash: AutoVacuum issue HOT 2
- [Bug]: Found empty chunks during upgrading. How to recover them? HOT 2
- Exclude osm chunks in show_chunk output HOT 1
- [Flaky test] job_errors_permissions
- [Enhancement]: Compression job should process chunks in order of range_start HOT 3
- NOTIFY / LISTEN on Hypertables HOT 4
- [Bug]: Foreign keys on compressed hypertables not working
- [Bug]: ERROR XX000 (internal_error) more than one invalidation watermark found HOT 2
- [Flaky test] chunk_utils HOT 1
- [Bug]: Correlation on chunks do not sum up into hypertable statistics HOT 2
- [Bug]: server crash: DETAIL: Failed process was running: autovacuum: ANALYZE _timescaledb_internal._hyper_1553_1989_chunk HOT 2
- [Bug]: DELETE FROM compressed chunks ignoring subquery HOT 7
- [Bug]: Update for single row on compressed hypertable tries to scan compressed chunks when using date_trunc or time_bucket HOT 1
- [Bug]: Attribute not suitable recommended for segment_by
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from timescaledb.