|
|
|
|
|
by ffsm8
61 days ago
|
|
Strange, you shouldn't have issues with vacuums on queue tables unless you're doing it wrong? Were you not using partitions like this? CREATE TABLE events_2026_04 PARTITION OF events
FOR VALUES FROM ('2026-04-01') TO ('2026-05-01'); CREATE TABLE events_2026_05 PARTITION OF events
FOR VALUES FROM ('2026-05-01') TO ('2026-06-01'); https://www.postgresql.org/docs/current/ddl-partitioning.htm... > Bulk loads and deletes can be accomplished by adding or removing partitions, if the usage pattern is accounted for in the partitioning design. Dropping an individual partition using DROP TABLE, or doing ALTER TABLE DETACH PARTITION, is far faster than a bulk operation. These commands also entirely avoid the VACUUM overhead caused by a bulk DELETE. It was a lot more annoying earlier then pg 13 though, maybe you're just reminiscing things from the 2010s? |
|