| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Brent Verner <brent(at)rcfile(dot)org> |
| Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Problem reloading regression database |
| Date: | 2002-01-14 05:41:11 |
| Message-ID: | 896.1010986871@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Brent Verner <brent(at)rcfile(dot)org> writes:
> | You'll need to make sure that the code isn't expecting to palloc
> | anything first-time-through and re-use it on later loops, but I
> | think that will be okay. (The attribute_buf is the most obvious
> | risk, but that's all right, see stringinfo.c.)
> So I /can't/ palloc some things /before/ switching context to
> per-tuple-context?
Oh, sure you can. That's the point of having a per-query context.
What I was wondering was whether there were any pallocs executed
*after* entering the loop that the code expected to live across
loop cycles. I don't think so, I'm just mentioning the risk as
part of your education ;-)
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andy Samuel | 2002-01-14 06:11:34 | Tablespace and clustering |
| Previous Message | Brent Verner | 2002-01-14 05:29:32 | Re: Problem reloading regression database |