Re: Double linking MemoryContext children

From: Jan Wieck <jan(at)wi3ck(dot)info>
To: Kevin Grittner <kgrittn(at)ymail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Double linking MemoryContext children
Date: 2015-09-14 12:24:34
Message-ID: 55F6BC82.4020801@wi3ck.info
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

Regards, Jan

--
Jan Wieck
Senior Software Engineer
http://slony.info

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Oleg Bartunov 2015-09-14 12:34:57 Re: WIP: Rework access method interface
Previous Message Tomas Vondra 2015-09-14 12:11:10 Re: On-demand running query plans using auto_explain and signals