It looks like I did not copy the list.
I did run VACUUM ANALYZE after the upgrade. I've even run it now
> before getting a new explain plan that is very similar (just the costs
> differ):
> Gather Merge (cost=12336145.92..16111570.23 rows=31531596 width=66)
>Workers Planned: 4
>-> Sort
On Mon, Jun 3, 2024 at 9:12 AM Greg Sabino Mullane
wrote:
> On Mon, Jun 3, 2024 at 6:19 AM Radu Radutiu wrote:
>
>> Do you have any idea how to further debug the problem?
>>
>
> Putting aside the issue of non-reclaimed memory for now, can you show us
> the actual query? The explain analyze you p
On Mon, Jun 3, 2024 at 6:19 AM Radu Radutiu wrote:
> Do you have any idea how to further debug the problem?
>
Putting aside the issue of non-reclaimed memory for now, can you show us
the actual query? The explain analyze you provided shows it doing an awful
lot of joins and then returning 14+ mi
Hello,
I have an out of memory problem after upgrading from postgresql 12 to 16.3.
I have identified one query that can reproduce the error on demand. Once
the query starts, it will eventually exhaust all RAM and swap until the OOM
killer will stop postgresql.
The setup is as follows:
- One VMWARE
