From: | Kevin Grittner <kgrittn(at)gmail(dot)com> |
---|---|
To: | "Peter J(dot) Holzer" <hjp-pgsql(at)hjp(dot)at> |
Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: plperlu stored procedure seems to freeze for a minute |
Date: | 2015-12-01 15:42:26 |
Message-ID: | CACjxUsOpgmFUJaohdCMcTV2oV9-j7xu5hJmuQXN7BT_4Jo2NLQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Tue, Dec 1, 2015 at 8:51 AM, Peter J. Holzer <hjp-pgsql(at)hjp(dot)at> wrote:
> What could cause a plperlu procedure to freeze for 68
> seconds between the call to confess and its output?
> Another weird thing: $success is undef because a ØMQ rpc call[1] timed
> out (after 60 seconds, which is also a mystery, because ØMQ doesn't seem
> to have a default timeout of 60 seconds, and I don't set one).
One thing I would check is the TCP keepalive settings.
If you don't sort it out, please read this and post with more
information; it's tough to guess at a cause without knowing the
version of PostgreSQL or the OS involved, etc.
https://wiki.postgresql.org/wiki/Guide_to_reporting_problems
--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | George Neuner | 2015-12-01 15:55:47 | Re: using a postgres table as a multi-writer multi-updater queue |
Previous Message | Alvaro Herrera | 2015-12-01 15:38:32 | Re: plperlu stored procedure seems to freeze for a minute |