On 07/10/2015 07:16 AM, Dave Page wrote:
> Are you able to get a stacktrace from a running instance that's hung?
Yes, but it's not doing anything, it's just polling for the next job.
> Also, does setting the logging level to debug reveal anything useful
> in the filesystem logs? (pgagent -l2
Sure Dave,
I will look into it.
Regards,
Sanket Mehta
Sr Software engineer
Enterprisedb
On Fri, Jul 10, 2015 at 7:40 PM, Dave Page wrote:
> Sanket - can you look at this please? As with Josh's request for
> --version, it looks like we added this functionality to the PEM agent,
> not pgAgent. Y
Sure Dave,
I will look into it.
Regards,
Sanket Mehta
Sr Software engineer
Enterprisedb
On Fri, Jul 10, 2015 at 7:39 PM, Dave Page wrote:
> Sanket - can you look at this please? It looks like we added this
> functionality to the PEM agent, but it really should be in pgAgent
> too. You may copy
On Tue, Jul 7, 2015 at 12:02 AM, Josh Berkus wrote:
> On 07/06/2015 10:26 AM, Josh Berkus wrote:
>> All,
>>
>> On the same server with the SQL errors (sequences are cleaned up now),
>> we're having pgagent start all jobs in the "r" state, log the first step
>> in each job in the "r" state, and the
Sanket - can you look at this please? As with Josh's request for
--version, it looks like we added this functionality to the PEM agent,
not pgAgent. You may copy the timestamp support for logging from the
PEM code to save effort.
On Sat, Jul 4, 2015 at 7:23 PM, Josh Berkus wrote:
> Request:
>
> p
Sanket - can you look at this please? It looks like we added this
functionality to the PEM agent, but it really should be in pgAgent
too. You may copy --version support from the PEM code to save effort.
On Sat, Jul 4, 2015 at 7:24 PM, Josh Berkus wrote:
> All:
>
> Currently pgagent does not have
