| From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
|---|---|
| To: | 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> |
| Cc: | PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Double linking MemoryContext children |
| Date: | 2015-12-07 01:30:56 |
| Message-ID: | 5664E150.6050406@BlueTreble.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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>
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim Nasby | 2015-12-07 01:37:20 | Re: Attach comments to functions' parameters and return value |
| Previous Message | Peter Geoghegan | 2015-12-07 00:45:02 | Re: Using quicksort for every external sort run |