BUG #18506: Memory Leak on wrong INNER JOINs

From: PG Bug reporting form <noreply(at)postgresql(dot)org>
To: pgsql-bugs(at)lists(dot)postgresql(dot)org
Cc: gts(dot)dmtr(at)gmail(dot)com
Subject: BUG #18506: Memory Leak on wrong INNER JOINs
Date: 2024-06-12 13:51:30
Message-ID: 18506-750a4469a5a97fa4@postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

The following bug has been logged on the website:

Bug reference: 18506
Logged by: D Goutis
Email address: gts(dot)dmtr(at)gmail(dot)com
PostgreSQL version: 14.6
Operating system: Ubuntu Linux 22.04
Description:

Greetings,

I do not know the severity of this bug. I stumbled up due to a typo ( `a`
instead of `ag`).
In a series of multiple INNER JOINS, I referenced wrongly another table and
the postgres docker container bloated a 64GB RAM.
The commented out line is the fix.
I could submit more details.

Regards,
Dimitris

```
CREATE OR REPLACE VIEW exampledb.vw_project_summary AS
SELECT
p.project_id
, p.project_name
, ag.unique_values AS implementing_agencies
FROM exampledb.mt_project p
INNER JOIN exampledb.vw_action_types_per_project a
ON (p.project_id = a.project_id)
INNER JOIN exampledb.vw_agencies_per_project ag
ON (p.project_id = a.project_id);
-- ON (p.project_id = ag.project_id);

```

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message David G. Johnston 2024-06-12 14:41:28 Re: BUG #18506: Memory Leak on wrong INNER JOINs
Previous Message Stefan Heine 2024-06-12 13:47:44 Re: BUG #18503: Reproducible 'Segmentation fault' in 16.3 on ARM64