Re: Problem with dblink - Mailing list pgsql-patches

From Tom Lane
Subject Re: Problem with dblink
Date
Msg-id 17790.1069881876@sss.pgh.pa.us
Whole thread Raw
In response to Re: Problem with dblink  (Joe Conway <mail@joeconway.com>)
Responses Re: Problem with dblink  (Joe Conway <mail@joeconway.com>)
Re: Problem with dblink  (Joe Conway <mail@joeconway.com>)
List pgsql-patches
Joe Conway <mail@joeconway.com> writes:
> Tom Lane wrote:
>> (More generally, I wonder if AtEOXact_SPI oughtn't be fixed to emit
>> a WARNING if the SPI stack isn't empty, except in the error case.
>> Neglecting SPI_finish is analogous to a resource leak, and we have
>> code in place to warn about other sorts of leaks.)

> I'll look at this separately. Changes in this regard only belong applied
> to cvs head I assume.

Yeah, I think to apply it to a stable branch you'd want some indication
that there are more live bugs out there that it's needed to catch.  At
the moment it only seems called for as an aid to future development, and
so HEAD seems sufficient.

            regards, tom lane

pgsql-patches by date:

Previous
From: Joe Conway
Date:
Subject: Re: Problem with dblink
Next
From: Joe Conway
Date:
Subject: Re: Problem with dblink