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: 2005-12-29 18:44:43
Message-ID: 22517.1135881883@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-patches

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

In response to

Responses

Browse pgsql-patches by date

  From Date Subject
Next Message Qingqing Zhou 2005-12-29 19:18:16 Re: Fix spinlock usage in UnpinBuffer()
Previous Message Tom Lane 2005-12-29 18:13:25 Re: Fix spinlock usage in UnpinBuffer()