The views on the database are sometimes slow with complex queries, especially when counting deletions - as in the "FIXME case" (counting removed FIXMEs).
Therefore, the PostgreSQL database must be specifically examined for performance bottlenecks by applying EXPLAIN ANALYZE and e.g. pgtune, type conversions (datetime) and read optimizations (e.g. CREATE UNLOGGED TABLE...).
Another hint (source: https://www.crunchydata.com/blog/performance-and-spatial-joins):
SHOW max_worker_processes; -- 8?
SHOW max_parallel_workers; -- 8?
SHOW max_parallel_workers_per_gather; -- 2?
SHOW min_parallel_table_scan_size; -- 8MB?
Then try
SET max_parallel_workers_per_gather = 8;
SET min_parallel_table_scan_size = '1kB';
The views on the database are sometimes slow with complex queries, especially when counting deletions - as in the "FIXME case" (counting removed FIXMEs).
Therefore, the PostgreSQL database must be specifically examined for performance bottlenecks by applying EXPLAIN ANALYZE and e.g. pgtune, type conversions (datetime) and read optimizations (e.g. CREATE UNLOGGED TABLE...).
Another hint (source: https://www.crunchydata.com/blog/performance-and-spatial-joins):
Then try