Skip site navigation (1) Skip section navigation (2)

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 (view raw or flat)
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

pgsql-bugs by date

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

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group