Frank van Vugt <ftm.van.v...@foxi.nl> writes:
> Any clues as to how to gather additional information that might bring us
> closer to a solution is appreciated also.
A stack trace from the point of the error would probably tell us a great
deal. Maybe you could attach to a backend with gdb, set a breakpoint
at the failure return in SPI_connect(), and then provoke the error
manually?
regards, tom lane
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
