On 06/07/2011 12:35 AM, Tom Lane wrote:
> Andrew Dunstan<andrew@dunslane.net> writes:
>> On 06/06/2011 07:30 PM, Robert Creager wrote:
>>> [4de65a8f.607a:3] LOG: statement: CREATE OR REPLACE FUNCTION bar() RETURNS integer AS $$
>>> #die 'BANG!'; # causes server process to exit(2)
>>> # alternative - causes server process to exit(255)
>>> spi_exec_query("invalid sql statement");
>>> $$ language plperl;
>>>
>>> I'll leave it running tonight (going home), so I can poke tomorrow if anyone wants me to.
>> That's weird. Why it should hang there I have no idea. Did it hang at
>> the same spot both times? Can you get a backtrace?
> 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.
It seems to be hung in Perl_get_hash_seed().
cheers
andrew