Andrew Dunstan <and...@dunslane.net> writes:
> On 06/07/2011 12:35 AM, Tom Lane wrote:
>> You sure it's hung on that statement, and not the following one?
>> The following one would be trying to load plperlu into a backend
>> already using plperl, which is an area that it wouldn't exactly
>> be surprising to find platform-dependent issues in.
> That's true, but he has log_statement = all, so the statement should be
> logged before it's executed. And the stack trace he's sent shows that's
> the statement being executed.
Yeah, the stack trace destroyed that theory.
> It seems to be hung in Perl_get_hash_seed().
Which is not our code, of course. Who wants to dig into perl guts?
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
