Postgres Pro
Downloads
Home   >   mailing lists

Re: memory leak in trigger handling (since PG12) - Mailing list pgsql-hackers

From Tomas Vondra
Subject Re: memory leak in trigger handling (since PG12)
Date
Msg-id ee964409-fc64-d7d2-d8ad-3a64b72b5dc4@enterprisedb.com
Whole thread Raw
In response to Re: memory leak in trigger handling (since PG12)  (Tomas Vondra <tomas.vondra@enterprisedb.com>)
Responses Re: memory leak in trigger handling (since PG12)
List pgsql-hackers
Tree view 
On 6/22/23 13:46, Tomas Vondra wrote:
> ...
> 
> I haven't tried the reproducer, but I think I see the issue - we store
> the bitmap as part of the event to be executed later, but the bitmap is
> in per-tuple context and gets reset. So I guess we need to copy it into
> the proper long-lived context (e.g. AfterTriggerEvents).
> 
> I'll get that fixed.
> 

Alexander, can you try if this fixes the issue for you?


regard

-- 
Tomas Vondra
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
Attachment

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Add GUC to tune glibc's malloc implementation.
Next
From: "Imseih (AWS), Sami"
Date:
Subject: New function to show index being vacuumed