[Bug]: INSERT INTO ... ON CONFLICT DO NOTHING on compressed chunks exits prematurely when encountering a conflict

[bjornuppeke]

What type of bug is this?

Incorrect result

What subsystems and features are affected?

Compression

What happened?

When inserting rows from a temporary table into a hypertable with compressed chunks, with INSERT INTO ... ON CONFLICT DO NOTHING, the transaction exits as soon as a conflict is encountered.

I expect the insert to continue with the next row.

TimescaleDB version affected

2.17.2

PostgreSQL version used

16

What operating system did you use?

docker.io/timescale/timescaledb-ha:pg16-ts2.17 on Mac OS ARM

What installation method did you use?

Docker

What platform did you run on?

Other

Relevant log output and stack trace

How can we reproduce the bug?

create database test;

\c test

CREATE TABLE main (
    id UUID NOT NULL,
    ts TIMESTAMPTZ NOT NULL,
    v FLOAT,
    PRIMARY KEY (id, ts)
);

SELECT create_hypertable('main', by_range('ts'));

ALTER TABLE main SET (timescaledb.compress, timescaledb.compress_orderby = 'ts DESC', timescaledb.compress_segmentby = 'id');

SELECT add_compression_policy('main', compress_after => INTERVAL '60d');

INSERT INTO main VALUES('BFE8F140-AF50-4FD9-BA16-43018AB2EE8A', '2023-01-01T14:00:00', '20');

CALL run_job(1000);

CREATE TABLE temp (LIKE main INCLUDING INDEXES);

DO $$
DECLARE
  start_ts TIMESTAMPTZ := '2023-01-01T00:00:00+0';
  end_ts TIMESTAMPTZ := start_ts + INTERVAL '1 month';
  current_ts TIMESTAMPTZ := start_ts; -- Changed variable name to current_ts
  random_value FLOAT;
BEGIN
  WHILE current_ts < end_ts LOOP
    random_value := random() * 100;

    INSERT INTO temp(id, ts, v)
    VALUES('BFE8F140-AF50-4FD9-BA16-43018AB2EE8A', current_ts, random_value);

    current_ts := current_ts + INTERVAL '1 hour';
  END LOOP;
END $$;

INSERT INTO main (SELECT * FROM temp) ON CONFLICT DO NOTHING;
>> INSERT 0 14