Dave Page <dp...@pgadmin.org> writes:
> Couldn't the callback have been called by another process though?
Hmm, maybe, if the messages got to the log out of order. Try
reproducing it with %p added to log_line_prefix.
> Anyhoo, here's the backtrace for the actual problem:
> ...
> perl510.dll!28028026()
>> plperl.dll!plperl_init_interp() Line 452 C
> plperl.dll!_PG_init() Line 229 C
> postgres.exe!internal_load_library(const char * libname=0x01372048)
> Line 287 C
Seems it's crashing inside perl_run(), which leaves us little wiser than
before :-(
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
