[Bug] VACUUM and VACUUM FULL appear to be ineffective on PAX tables.
@gfphoenix78 ya está trabajando en esto.
Desde el 24/6/2026.
Evaluación
Este issue todavía no se ha evaluado.
Descripción
Apache Cloudberry version
2.1
What happened
After inserting a large amount of data into a PAX table and deleting most of the rows, running either VACUUM or VACUUM FULL does not reduce the table size / disk usage.
What you think should happen instead
- VACUUM should reclaim or compact storage occupied by deleted rows, if supported.
- VACUUM FULL should reclaim the space more aggressively, likely by rewriting/compacting the table.
- If VACUUM / VACUUM FULL is currently unsupported for PAX tables, Cloudberry should return a clear warning/error instead of silently doing nothing.
How to reproduce
DROP TABLE IF EXISTS pax_vacuum_repro;
CREATE TABLE pax_vacuum_repro (
id int,
payload text
) USING PAX
DISTRIBUTED BY (id);
INSERT INTO pax_vacuum_repro
SELECT
g,
repeat(md5(g::text), 50)
FROM generate_series(1, 5000000) AS g;
-- Check initial row count and size.
SELECT count(*) FROM pax_vacuum_repro;
SELECT pg_size_pretty(pg_total_relation_size('pax_vacuum_repro')) AS size_before_delete;>
-- Delete most rows.
DELETE FROM pax_vacuum_repro
WHERE id <= 4500000;
SELECT count(*) FROM pax_vacuum_repro;
SELECT pg_size_pretty(pg_total_relation_size('pax_vacuum_repro')) AS size_after_delete;
analyze pax_vacuum_repro;
-- Try normal VACUUM.
VACUUM pax_vacuum_repro;
analyze pax_vacuum_repro;
SELECT pg_size_pretty(pg_total_relation_size('pax_vacuum_repro')) AS size_after_vacuum;
-- Try VACUUM FULL.
VACUUM FULL pax_vacuum_repro;
analyze pax_vacuum_repro;
SELECT pg_size_pretty(pg_total_relation_size('pax_vacuum_repro')) AS size_after_vacuum_full;
Operating System
rocky 9.6
Anything else
No response
Are you willing to submit PR?
- Yes, I am willing to submit a PR!
Code of Conduct
- I agree to follow this project's Code of Conduct.
- Lenguaje dominante
- C
- Estrellas
- 1.4k
- Forks
- 248
- Merge medio
- 4 d 10 h
- PR fusionados (30 d)
- 40
Guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de apache/cloudberry
-
type: Bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
apache/cloudberry#1885 · 2 reacciones ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 86/100
apache/cloudberry#1825 ·
-
type: Bug
Dificultad 3/5 1-2 días Aptitud para principiantes 65/100
apache/cloudberry#2048 · 1 reacción ·
-
type: Bug
Dificultad 4/5 3-5 días Aptitud para principiantes 40/100
apache/cloudberry#2047 ·
-
type: Bug
Dificultad 4/5 3-5 días Aptitud para principiantes 45/100
apache/cloudberry#2046 · 1 comentario ·
Todos los issues de apache/cloudberry
Issues similares
-
Dificultad 2/5 1-2 días Aptitud para principiantes 78/100
brunodev85/gladio#18 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
OpenPrinting/cups#1721 ·
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 88/100
zephyrproject-rtos/zephyr#120318 · 1 comentario ·
-
issue: bug report
Dificultad 1/5 Menos de una hora Aptitud para principiantes 90/100
-
[BUG] [25.12.5] Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100