| 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-17 16:17:56 |
| Message-ID: | 2759.1247847476@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:
> So this took a while, but here's your test case.....
> Turns out to be quite small actually ;)
Hmm ... the relevant code change seems to have been
http://archives.postgresql.org/pgsql-committers/2009-04/msg00127.php
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.
regards, tom lane
| Attachment | Content-Type | Size |
|---|---|---|
| unknown_filename | text/plain | 860 bytes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2009-07-17 17:05:17 | Re: BUG #4926: too few pathkeys for mergeclauses |
| Previous Message | Greg Stark | 2009-07-17 16:12:28 | Re: Huge speed penalty using <>TRUE instead of =FALSE |