| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | Asif Naeem <asif(dot)naeem(at)enterprisedb(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: plpython crash (PG 92) |
| Date: | 2012-04-27 22:51:02 |
| Message-ID: | 4421.1335567062@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> I must have been confused about the tuple descriptor APIs. ob->tupdesc
> is created using CreateTupleDescCopy(), which copies the refcount of the
> original tuple descriptor,
Um, surely not. That would be nonsensical, and anyway a look at the
code shows it isn't doing that.
> thus causing a failure when the (seemingly still referenced) tupdesc
> is freed. Is this behavior correct and useful?
I think there must be some mistake in your analysis.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Grittner | 2012-04-27 22:58:48 | Re: Re: xReader, double-effort (was: Temporary tables under hot standby) |
| Previous Message | Christopher Browne | 2012-04-27 22:50:06 | Re: Future In-Core Replication |