Search Postgresql Archives

Re: plperlu stored procedure seems to freeze for a minute

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Peter J. Holzer wrote:

> Two messages from the same line of the same plperlu stored procedure, 68
> seconds apart. So what is this line 36?
> 
>     confess "impossible result '$success' (payload=$payload)";
> 
> What? The first message clearly comes from interpolating $success
> (which is undef at that point) into the argument. The second from
> confess itself. What could cause a plperlu procedure to freeze for 68
> seconds between the call to confess and its output?

Try running it under strace.  Maybe it's trying to resolve some name and
its resolver takes a minute to discover it can't, or something like that.

-- 
Álvaro Herrera                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services


-- 
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general



[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux