GitHub user igor-suhorukov added a comment to the discussion: [Proposal] Apache Cloudberry as PostgreSQL 19 Extensions
@yjhjstz @leborchuk thank you for sharing your expert opinion! @yjhjstz thanks, point 2 is fair, so I took it as a test plan. Today the port runs 60 of the 262 tests in isolation2_schedule, plus 14 of the 15 parallel retrieve cursor tests. These are the ones on distributed transactions, snapshots, locks, GDD, FTS and mirrors, and each runs under the planner and under ORCA. Among them, reader_waits_for_lock reaches XactAdoptTransactionState(), under ORCA. distributed_snapshot, distributedlog-bug and gdd/concurrent_update reach the hidden-commit path. vacuum_recently_dead_tuple_due_to_distributed_snapshot reaches the slot. None of Cloudberry's tests reaches a segment waiting on a prepared part. Cloudberry's coordinator PANICs rather than end a transaction with a part still prepared, so its tests never get there. I added tests for it. Added after your comment: 1. igor-suhorukov/cloudberry@3f2b6df967a: fix. A lost wake-up of the recovery process could leave a prepared part, and every reader on its segment, waiting 5 minutes. 2. igor-suhorukov/cloudberry@d054391a681: isolation2 port/dtx_wait_prepared. A reader waits on a segment for a prepared part (336 s before the fix, 35 s after). 3. igor-suhorukov/cloudberry@3dbbc77a1b0: isolation2 port/dtx_horizon. The VACUUM test runs with and without the slot (38/37/25 rows vs 0/37/25), as a negative control. 4. igor-suhorukov/cloudberry@76bb3ae76ef: combocid_readers. combocid_gp's checks, counted, with ORCA's readers asserted. 5. igor-suhorukov/cloudberry@ac1eb409d76: dtm_retry's skip reason corrected. Full run on that commit: isolation2 80/80 in both passes, greenplum_schedule 392/392 and 394/394. Still to do: the other 200 isolation2 tests (133 of them append-optimized) and latency and concurrency benchmarks (your point 3). GitHub link: https://github.com/apache/cloudberry/discussions/2065#discussioncomment-18708218 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
