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: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: bug or simply not enough stack space?
Date: 2009-07-16 14:30:28
Message-ID: 200907161630.29119.ftm.van.vugt@foxi.nl (view raw or flat)
Thread:
Lists: pgsql-bugs
Hi,

> > WARNING: AbortSubTransaction while in ABORT state
> > WARNING: did not find subXID 75610 in MyProc
> > ERROR: tupdesc reference 0x7ffe74eaf028 is not owned by resource owner
> > SubTransaction
>
> 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? That we could do 
immediately ;)




-- 
Best,




Frank.


In response to

Responses

pgsql-bugs by date

Next:From: Tom LaneDate: 2009-07-16 14:36:59
Subject: Re: bug or simply not enough stack space?
Previous:From: Tom LaneDate: 2009-07-16 14:04:26
Subject: Re: bug or simply not enough stack space?

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