On Wed, 7 Sept 2022 at 13:33, Levi Aul wrote:
> To be clear, this isn't a bug report. There is no bug—everything is working
> exactly as it should. The partitions are not being pruned because the
> workload consists of OLAP aggregations that fetch a small number of rows
> spread across all part
We're using Postgres 14.5. I meant partition pruning.
To be clear, this isn't a bug report. There is no bug—everything is working
exactly as it should. The partitions are not being pruned because the
workload consists of OLAP aggregations that fetch a small number of rows
spread across all partiti
On Wed, 7 Sept 2022 at 07:40, Levi Aul wrote:
> In other words, our workload is inherently one that acquires "way too many
> locks." Our largest performance bottleneck, according to pg_wait_sampling, is
> the LockManager itself. Despite most of our queries spending only
> milliseconds actually
By "SEALED", do you mean "READ ONLY"?
On 9/6/22 14:39, Levi Aul wrote:
My company runs some large OLAP data warehouses with append-only,
time-partitioned datasets. Our workloads involve aggregations and joins,
and query the data in ways not amenable to constraint-exclusion; and we
serve a high
