What happens?

When the index is merging, the process cannot be interrupted unless you kill Postgres entirely. This is because the merge process holds an LwLock on a buffer, and Postgres doesn't receive interrupts while that lock is being held.

To Reproduce

1. Create and index a large table.
2. Set target_segment_count to be half of whatever it currently is.
3. Run a VACUUM, which should trigger a merge process down to target_segment_count.
4. Try to kill the process with Ctrl C.

OS:

macOS

ParadeDB Version:

0.14.0

Are you using ParadeDB Docker, Helm, or the extension(s) standalone?

ParadeDB pg_search Extension

Full Name:

Ming

Affiliation:

ParadeDB

Did you include all relevant data sets for reproducing the issue?

Yes

Did you include the code required to reproduce the issue?

• Yes, I have

Did you include all relevant configurations (e.g., CPU architecture, PostgreSQL version, Linux distribution) to reproduce the issue?

• Yes, I have