| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | pgsql-hackers(at)postgreSQL(dot)org |
| Subject: | Re: Bogus sizing parameters in some AllocSetContextCreate calls |
| Date: | 2016-08-27 19:36:28 |
| Message-ID: | 24859.1472326588@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andres Freund <andres(at)anarazel(dot)de> writes:
> On 2016-08-27 14:08:44 -0400, Tom Lane wrote:
>> Barring objection, I propose to make these changes in HEAD and 9.6.
> I think we might also / instead want to think about replacing a lot of
> those AllocSetContextCreate with a wrapper function. Currently is really
> rather annoying to experiment with switching the default allocator
> out. And if we're touching all that code anyway ...
I do not see why you'd think that "switching the default allocator out"
requires anything except making AllocSetContextCreate do something else.
What is actually of interest, IMO, is making *some* contexts have a
different allocator, and that is going to require case-by-case decisions
anyway. A blanket switch seems completely useless to me.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2016-08-27 19:40:10 | Re: Bogus sizing parameters in some AllocSetContextCreate calls |
| Previous Message | Andres Freund | 2016-08-27 19:09:33 | Re: Bogus sizing parameters in some AllocSetContextCreate calls |