On Jan 18, 2012, at 6:34 AM, Dave Page wrote:
>> Realized this when *neither* step ran last night. That certainly feels like
>> a bug to me: if I have the “End” field blank (NULL), it should remain blank
>> unless I set it.
>
> Agreed - I've committed a fix for this.
>
>>> In any event, I woul
On Mon, Jan 16, 2012 at 6:16 PM, David E. Wheeler wrote:
> On Jan 16, 2012, at 9:05 AM, David E. Wheeler wrote:
>
>> postgres=# select * from pgagent.pga_jobsteplog where jslid = 284;
>> -[ RECORD 1 ]--
>> jslid | 284
>> jsljlgid | 211
>> jsljstid | 1
>> js
On Jan 17, 2012, at 9:17 AM, Dave Page wrote:
>> It’s the standard schema, I think. Attached.
>
> I really wanted the data in it :-)
Oh, you didn’t say that. Will send privately in a mo.
David
--
Sent via pgadmin-support mailing list (pgadmin-support@postgresql.org)
To make changes to your s
On Tue, Jan 17, 2012 at 5:15 PM, David E. Wheeler wrote:
> On Jan 17, 2012, at 2:47 AM, Dave Page wrote:
>
>> Can you get me a dump of the pgagent schema please?
>
> It’s the standard schema, I think. Attached.
I really wanted the data in it :-)
--
Dave Page
Blog: http://pgsnake.blogspot.com
Tw
On Jan 17, 2012, at 2:47 AM, Dave Page wrote:
> Can you get me a dump of the pgagent schema please?
It’s the standard schema, I think. Attached.
Best,
David
pgagent.sql
Description: Binary data
--
Sent via pgadmin-support mailing list (pgadmin-support@postgresql.org)
To make changes to y
Can you get me a dump of the pgagent schema please?
On Mon, Jan 16, 2012 at 6:16 PM, David E. Wheeler wrote:
> On Jan 16, 2012, at 9:05 AM, David E. Wheeler wrote:
>
>> postgres=# select * from pgagent.pga_jobsteplog where jslid = 284;
>> -[ RECORD 1 ]--
>> jslid
On Jan 16, 2012, at 9:05 AM, David E. Wheeler wrote:
> postgres=# select * from pgagent.pga_jobsteplog where jslid = 284;
> -[ RECORD 1 ]--
> jslid | 284
> jsljlgid| 211
> jsljstid| 1
> jslstatus | s
> jslresult | 0
> jslstart| 2012-01-13 01:06:05
On Jan 16, 2012, at 7:45 AM, Dave Page wrote:
> Depends on what the first step is doing. You have On Error set to Fail, which
> will cause subsequent steps to be skipped if an error is detected. What do
> you see in the job step log for the first step?
Success:
postgres=# select * from pgage
Hi
On Sun, Jan 15, 2012 at 7:18 PM, David E. Wheeler wrote:
> pgAdmins,
>
> I added a new step to a pgAgent job a couple days ago, but noticed it has
> not been executing. It is listed under the job's steps in the pgAdmin
> object browser, as shown in the attached screenshot. However, when I vie
