Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: pl/python: fix ref leak on elog
- From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
- To: Neil Conway <neilc(at)samurai(dot)com>
- Cc: PostgreSQL-patches <pgsql-patches(at)postgresql(dot)org>
- Subject: Re: pl/python: fix ref leak on elog
- Date: Thu, 29 Dec 2005 13:44:43 -0500
- Message-id: <22517.1135881883@sss.pgh.pa.us> <text/plain>
Neil Conway <neilc(at)samurai(dot)com> writes: > Since the problem might actually occur in practice and the fix seems to > have little chance of inducing a regression, I'm thinking of applying > this to both HEAD and back branches. Barring any objections I'll do that > later today or early tomorrow. Looks alright to me. I agree with backpatching as far back as we have PG_TRY. The reason for the FIXME was that there wasn't any simple way to fix it before that ... regards, tom lane
- Follow-Ups:
- Re: pl/python: fix ref leak on elog
- From: Neil Conway
- Re: pl/python: fix ref leak on elog
- References:
- pl/python: fix ref leak on elog
- From: Neil Conway
- pl/python: fix ref leak on elog
- Prev by Date: Re: Fix spinlock usage in UnpinBuffer()
- Next by Date: Re: Fix spinlock usage in UnpinBuffer()
- Previous by thread: pl/python: fix ref leak on elog
- Next by thread: Re: pl/python: fix ref leak on elog
- Indexes: