Re: bug or simply not enough stack space?

From: Frank van Vugt <ftm(dot)van(dot)vugt(at)foxi(dot)nl>
To: pgsql-bugs(at)postgresql(dot)org
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: Re: bug or simply not enough stack space?
Date: 2009-07-16 15:28:54
Message-ID: 200907161728.55367.ftm.van.vugt@foxi.nl
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Op donderdag 16 juli 2009, schreef Tom Lane:
> >> Those are bugs (although there is probably only one bug and the rest is
> >> collateral damage). May we have a test case?
> >
> > Scripts, triggers and stuff are a bit complex, before assigning the
> > resources for that, could we help with creating a backtrace?
>
> You did show a backtrace --- it proves only what was already obvious,
> namely that the problem is in transaction cleanup.

Ok, working on it.

--
Best,

Frank.

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Steve Caligo 2009-07-16 16:34:13 BUG #4925: "select ... for update" doesn't affect rows from sub-query
Previous Message Tom Lane 2009-07-16 14:36:59 Re: bug or simply not enough stack space?