Re: Performance problem in aset.c

From: Philip Warner <pjw(at)rhyme(dot)com(dot)au>
To: Alfred Perlstein <bright(at)wintelcom(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Jan Wieck <JanWieck(at)Yahoo(dot)com>, Karel Zak <zakkr(at)zf(dot)jcu(dot)cz>, pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: Performance problem in aset.c
Date: 2000-07-12 06:30:10
Message-ID: 3.0.5.32.20000712163010.01feebb0@mail.rhyme.com.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

At 22:33 11/07/00 -0700, Alfred Perlstein wrote:
>
>The only time you may want to do this is if you're doing a special purpose
>allocator like a zone or slab allocator, otherwise it's a pessimization.

That is why it is done (I believe) - memory can be allocated using one
context then freed as a block when the context is no longer used.

----------------------------------------------------------------
Philip Warner | __---_____
Albatross Consulting Pty. Ltd. |----/ - \
(A.C.N. 008 659 498) | /(@) ______---_
Tel: (+61) 0500 83 82 81 | _________ \
Fax: (+61) 0500 83 82 82 | ___________ |
Http://www.rhyme.com.au | / \|
| --________--
PGP key available upon request, | /
and from pgp5.ai.mit.edu:11371 |/

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Alfred Perlstein 2000-07-12 06:30:49 Re: Connection pooling.
Previous Message Philip Warner 2000-07-12 06:22:10 Re: Connection pooling.