From: | Brent Verner <brent(at)rcfile(dot)org> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
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 04:34:44 |
Message-ID: | 20020114043444.GA3618@rcfile.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
[2002-01-13 22:51] Tom Lane said:
| Brent Verner <brent(at)rcfile(dot)org> writes:
| > I must retract this assertion. As posted, this patch dies on the
| > second line of a COPY file... argh. What did I break?
|
| First guess is that you allocated some data structure in the per-tuple
| context that needs to be in the per-query context (ie, needs to live
| throughout the copy).
yup. The problem sneaks up when I get a default value for a "text"
column via ExecEvalExprSwithContext. Commenting out the pfree above
heap_formtuple makes the error go away, but I know that's not the
right answer. Should I avoid freeing the !attbyval items when they've
come from ExecEvalExpr -- I don't see any other examples of freeing
returns from this fn.
b
--
"Develop your talent, man, and leave the world something. Records are
really gifts from people. To think that an artist would love you enough
to share his music with anyone is a beautiful thing." -- Duane Allman
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2002-01-14 05:03:43 | Re: Problem reloading regression database |
Previous Message | Tom Lane | 2002-01-14 04:30:15 | Re: Release time |