From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Maxim Boguk <maxim(dot)boguk(at)gmail(dot)com> |
Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #5798: Some weird error with pl/pgsql procedure |
Date: | 2011-02-19 16:08:13 |
Message-ID: | 28329.1298131693@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Maxim Boguk <maxim(dot)boguk(at)gmail(dot)com> writes:
> I finally managed create working slave server with non-stripped Postgresql
> 8.4.7 and working gdb.
> (sorry for such long delay).
> And i can reproduce situation quite easy now, so i managed get stack
> backtrace with that error.
> What i need to do now? I have some expirience with gbd now but i have no
> idea where to look next.
Now that you know what query is causing the problem:
> #9 0x0000000000673d43 in ProcessQuery (plan=0xdd0998890,
> sourceText=0xdd09c5830 "UPDATE ONLY bill.ctrl_servers SET opt = opt
> WHERE ctid=ANY($1) RETURNING ctid", params=0xdd09c58c0,
> dest=0xdd09de5c8, completionTag=0x7fffffffd4e0 "") at pquery.c:196
it shouldn't be too hard to prepare a self-contained test case so that
others can look at this.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Maxim Boguk | 2011-02-19 23:01:38 | Re: BUG #5798: Some weird error with pl/pgsql procedure |
Previous Message | Maxim Boguk | 2011-02-19 13:05:17 | Re: BUG #5798: Some weird error with pl/pgsql procedure |