Files
DocsGPT/application/storage
Alex fdba261d11 fix(db): make compression-point deduplication atomic
The duplicate check for append_compression_point ran as a SELECT before
the UPDATE, so two sessions persisting the same point could both pass it.
The predicate now lives inside the UPDATE's CASE expression and is
evaluated under the row lock; a point without query_index or
compressed_summary never matches and is always appended. Adds a
two-session regression test that races the same point and expects one.
2026-09-05 09:49:22 +01:00
..
2026-08-12 12:36:43 +01:00
2026-08-29 12:06:00 +01:00