Re: Error: dsa_area could not attach to a segment that has been freed

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Craig Ringer <craig(at)2ndquadrant(dot)com>
Cc: Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>, Gaddam Sai Ram <gaddamsairam(dot)n(at)zohocorp(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Error: dsa_area could not attach to a segment that has been freed
Date: 2017-09-20 13:37:10
Message-ID: 5111.1505914630@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Craig Ringer <craig(at)2ndquadrant(dot)com> writes:
> On 20 September 2017 at 16:55, Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>
> wrote:
>> There is a kind of garbage collection for palloc'd memory and
>> also for other resources like file handles, but if you're using a big
>> long lived DSA area you have nothing like that.

> We need, IMO, a DSA-backed heirachical MemoryContext system.

Perhaps the ResourceManager subsystem would help here.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2017-09-20 13:42:08 Re: SCRAM in the PG 10 release notes
Previous Message Peter Eisentraut 2017-09-20 13:35:06 Re: [PATCH] Generic type subscripting