2009/7/14 Frank van Vugt <ftm.van.v...@foxi.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 -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
