Re: Bound memory usage during manual slot sync retries - Mailing list pgsql-hackers

From Amit Kapila
Subject Re: Bound memory usage during manual slot sync retries
Date
Msg-id CAA4eK1L=P+4hdnic8gQ1QFL9KZiM_mReCNTYWx99ct23mCoZ8g@mail.gmail.com
Whole thread
In response to Re: Bound memory usage during manual slot sync retries  (Amit Kapila <amit.kapila16@gmail.com>)
Responses Re: Bound memory usage during manual slot sync retries
List pgsql-hackers
On Mon, May 25, 2026 at 7:03 PM Amit Kapila <amit.kapila16@gmail.com> wrote:
>
> Okay, then let's go with a per-retry memory context approach.
>
> @@ -579,6 +579,8 @@ drop_local_obsolete_slots(List *remote_slot_list)
>      local_slot->data.database));
>   }
>   }
> +
> + list_free(local_slots);
>  }
>
> Why do we need this retail pfree if the caller is using memory context?
>

I see that the latest patch in email [1] has already addressed this
point. So, I'll push the v2 version.

[1] - https://www.postgresql.org/message-id/CABPTF7WB4Z62sPoZkhSygOCAo3OiTDLpMELxZDuwCb3HYgM_pQ%40mail.gmail.com

--
With Regards,
Amit Kapila.



pgsql-hackers by date:

Previous
From: Paul A Jungwirth
Date:
Subject: Re: Fix bug of UPDATE/DELETE FOR PORTION OF with inheritance tables
Next
From: Nathan Bossart
Date:
Subject: expand refint docs with usage info