| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Joe Conway <mail(at)joeconway(dot)com> |
| Cc: | "Patches (PostgreSQL)" <pgsql-patches(at)postgresql(dot)org>, Andrea Grassi <andreagrassi(at)sogeasoft(dot)com>, Darko(dot)Prenosil(at)finteh(dot)hr, shridhar_daithankar(at)persistent(dot)co(dot)in |
| Subject: | Re: Problem with dblink |
| Date: | 2003-11-26 21:24:36 |
| Message-ID: | 17790.1069881876@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-patches |
Joe Conway <mail(at)joeconway(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joe Conway | 2003-11-26 22:39:35 | Re: Problem with dblink |
| Previous Message | Joe Conway | 2003-11-26 20:46:30 | Re: Problem with dblink |