On Thu, 2025-04-10 at 14:46 +0200, Daniel Gustafsson wrote:
> > On 10 Apr 2025, at 13:42, Laurenz Albe wrote:
> > > +extern dsa_area *area;
> >
> > This commit causes problems for PostGIS, because the name "area" collides
> > with a PostGIS object:
>
> Thanks for the report, I've already posted
> On 10 Apr 2025, at 13:42, Laurenz Albe wrote:
> On Tue, 2025-04-08 at 09:10 +, Daniel Gustafsson wrote:
>> +extern dsa_area *area;
>
> This commit causes problems for PostGIS, because the name "area" collides
> with a PostGIS object:
Thanks for the report, I've already posted a patch [0]
Hi,
> Now one can take the position that PostGIS as dependent library hs to
> adapt, but I think "area" is too generic a name. Could you envision
> renaming the global variable to something like "shm_area"?
>
> Attached is a patch for this change.
> I am not wedded to the name at all, it was just
On Tue, 2025-04-08 at 09:10 +, Daniel Gustafsson wrote:
> Add function to get memory context stats for processes
>
> This adds a function for retrieving memory context statistics
> and information from backends as well as auxiliary processes.
> The intended usecase is cluster debugging when un
Add function to get memory context stats for processes
This adds a function for retrieving memory context statistics
and information from backends as well as auxiliary processes.
The intended usecase is cluster debugging when under memory
pressure or unanticipated memory usage characteristics.
Wh
