| From: | Thom Brown <thom(at)linux(dot)com> |
|---|---|
| To: | Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com> |
| Cc: | Jan Wieck <jan(at)wi3ck(dot)info>, Kevin Grittner <kgrittn(at)ymail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Double linking MemoryContext children |
| Date: | 2015-12-08 23:40:43 |
| Message-ID: | CAA-aLv6YKSovwBVGFjDYBktTUatTFYcMkhFOjxLBQGaP88GEnw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 7 December 2015 at 01:30, Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com> wrote:
> On 9/14/15 7:24 AM, Jan Wieck wrote:
>>
>> On 09/12/2015 11:35 AM, Kevin Grittner wrote:
>>
>>> On the other hand, a grep indicates that there are two places that
>>> MemoryContextData.nextchild is set (and we therefore probably need
>>> to also set the new field), and Jan's proposed patch only changes
>>> one of them. If we do this, I think we need to change both places
>>> that are affected, so ResourceOwnerCreate() in resowner.c would
>>> need a line or two added.
>>
>>
>> ResourceOwnerCreate() sets ResourceOwnerData.nextchild, not
>> MemoryContextData.nextchild.
>
>
> Anything ever happen with this? </Momjian-Mode>
Yeah, it was committed... a few mins ago.
Thom
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2015-12-08 23:41:28 | Re: HELP!!! The WAL Archive is taking up all space |
| Previous Message | Jim Nasby | 2015-12-08 23:39:35 | Re: Fwd: Another little thing about psql wrapped expanded output |