Re: SPI_ERROR_CONNECT within pl/pgsql, PG 8.4

From: Marek Lewczuk <marek(at)lewczuk(dot)com>
To: Frank van Vugt <ftm(dot)van(dot)vugt(at)foxi(dot)nl>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: SPI_ERROR_CONNECT within pl/pgsql, PG 8.4
Date: 2009-07-14 12:54:12
Message-ID: daadfdc20907140554k5c3a3e43lbdde4cafb9721762@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

2009/7/14 Frank van Vugt <ftm(dot)van(dot)vugt(at)foxi(dot)nl>:
> Hi,
>
>> This is a normal interbackend communication signal.  You need to
>> configure gdb to ignore SIGUSR2 (ie, pass it on and not stop execution).
>> Probably SIGUSR1 too.
Frank,
thanks for letting me know about your post - I didn't have time yet to
read yesterday posts, but I'm glad that I'm not only one who is
experiencing that problem :-). Thanks for the backtrace - I hope that
Tom will find the reason of that error. Could you please send me gdb
commands - I could also provide the backtrace, so Tom would have wider
view of what is happening.

Marek

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Frank van Vugt 2009-07-14 13:18:15 Re: SPI_ERROR_CONNECT within pl/pgsql, PG 8.4
Previous Message Lauris Ulmanis 2009-07-14 12:39:10 BUG #4919: CREATE USER command slows down system performance