From: | Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Re: Memory leak in incremental sort re-scan |
Date: | 2023-06-15 22:34:54 |
Message-ID: | c4df75a8-b274-9a65-8815-74de587865b7@enterprisedb.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 6/15/23 22:36, Tom Lane wrote:
> Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com> writes:
>> On 6/15/23 22:11, Tom Lane wrote:
>>> I see zero leakage in that example after applying the attached quick
>>> hack. (It might be better to make the check in the caller, or to just
>>> move the call to ExecInitIncrementalSort.)
>
>> Thanks for looking. Are you planning to work on this and push the fix,
>> or do you want me to finish this up?
>
> I'm happy to let you take it -- got lots of other stuff on my plate.
>
OK, will do.
--
Tomas Vondra
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2023-06-15 22:41:51 | Re: subscription/033_run_as_table_owner is not listed in the meson.build |
Previous Message | Masahiko Sawada | 2023-06-15 22:15:36 | Re: subscription/033_run_as_table_owner is not listed in the meson.build |