On 3/5/2012 7:26 AM, Dave Page wrote:
>>>>> The step or the job shows as failed? What's the output from the step?
>>>> Both the step and the job are shown as failed. Thanks.
>>> And the step output?
>> I think you are referring to the "Output" column in the Statistics tab.
>> That column is completely blank for all tests.
> Can you confirm from the server log (on the server on which the step
> runs), that the step does actually run or not?
> Assuming it does, try running pgAgent with the log level increased to
> WARNING to see if anything shows up there.
Ok, I finally figured this out. The step does run; using the sample job
I provided, the table is updated with the current date. In my original
post, I provided the output of a DEBUG run; that should have had at
least as much detail as WARNING, yes?
At any rate, the problem was (drum roll...) I neglected to put a commit
after my update statement in the job step SQL. After doing so, the job
and step are both successful.
So now the only thing odd is that the update actually *was* committed,
even the job indicated it had failed. I say this because the updated
value persisted between reboots.
Thanks for persisting, Dave.
In response to
pgadmin-support by date
|Next:||From: Colin Beckingham||Date: 2012-03-06 14:19:36|
|Subject: View create usage|
|Previous:||From: Guillaume Lelarge||Date: 2012-03-05 21:32:59|
|Subject: Re: pgadmin 1.14.2, ERROR:column tgconstraint
does not exist|