| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Frank van Vugt <ftm(dot)van(dot)vugt(at)foxi(dot)nl> |
| Cc: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: bug or simply not enough stack space? |
| Date: | 2009-07-18 19:17:46 |
| Message-ID: | 12939.1247944666@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Frank van Vugt <ftm(dot)van(dot)vugt(at)foxi(dot)nl> writes:
>> I think I might have been overenthusiastic in trying to free resources
>> during a subtransaction abort. Try this patch and see if you notice
>> any bad side-effects.
> All examples I had that crashed and burned, now work correctly and/or bail out
> correctly where needed.
> No side-effects noticed.
Well, it had some :-(. I've committed a better version of that patch,
which will be in 8.4.1. However, if you're not seeing any serious
memory leakage then you could keep using the patch you have for the
time being.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jaime Casanova | 2009-07-20 06:58:56 | Re: fix: plpgsql: return query and dropped columns problem |
| Previous Message | Euler Taveira de Oliveira | 2009-07-18 02:09:54 | Re: BUG #4927: psql does "spoil" the query before sending it to server |