You've already forked mariadb-columnstore-engine
mirror of
https://github.com/mariadb-corporation/mariadb-columnstore-engine.git
synced 2026-10-23 21:49:05 +03:00
6ccb90443f
The master segment table existed to hold a reader-writer lock and a size for each structure in shared memory, that are not needed in the versioned schema. So the table goes, and with it RWLockMonitor - four threads per worker whose whole job was to watch those locks for owners that had died, a question the robust mutex answers by itself. refreshShmWithLock() goes too. It existed so a reader could be sure it was not looking at a stale mapping; a reader now follows the published id on every pin and cannot be stale. mcs-shmem-locks keeps its command line and reports no locks held, so cmapi's release_shmem_locks() goes on working against a cluster that has no such locks to release.