Re: pgAgent job step reporting failure when batch command succeeds - Mailing list pgadmin-support

From Martin French
Subject Re: pgAgent job step reporting failure when batch command succeeds
Date
Msg-id OF5BA533AC.D3275C14-ON80257A5C.0023C21D-80257A5C.0024106D@LocalDomain
Whole thread Raw
In response to pgAgent job step reporting failure when batch command succeeds  (osleep <osleep@docfocus.ca>)
List pgadmin-support
<p><tt><font size="2">> From: osleep <osleep@docfocus.ca></font></tt><br /><tt><font size="2">> To:
pgadmin-support@postgresql.org,</font></tt><br /><tt><font size="2">> Date: 15/08/2012 18:44</font></tt><br
/><tt><fontsize="2">> Subject: [pgadmin-support] pgAgent job step reporting failure when <br />> batch command
succeeds</font></tt><br/><tt><font size="2">> Sent by: pgadmin-support-owner@postgresql.org</font></tt><br
/><tt><fontsize="2">> <br />> Hey there,<br />> <br />> I am running PostgreSQL 9.0.8 and the latest
versionof pgAgent available<br />> through the Application StackBuilder using Windows Server 2003 Service Pack<br
/>>2.<br />> <br />> I have a job that has one batch command step that continually fails even<br />> though
thebatch command is successful. When I checked the pga_jobsteplog, I<br />> find that the line pertaining to the job
stepcontains the call used to<br />> execute the batch command and nothing else.<br />> <br />> Normally I've
foundthat batch steps report null unless there is an error.<br />> Is this causing pgAgent to consider the job step
failed?<br/>> <br />> Thanks,<br />> Owen Sleep<br />> <br />> <br />Hi Owen,</font></tt><br /><br
/><tt><fontsize="2">I've patched this and it should be available in the next version of pgAgent.</font></tt><br /><a
href="http://archives.postgresql.org/pgadmin-hackers/2012-07/msg00098.php"><fontcolor="#0000FF" face="serif"
size="3"><u>http://archives.postgresql.org/pgadmin-hackers/2012-07/msg00098.php</u></font></a><fontface="serif"
size="3"> </font><br/><br /><tt><font size="2">Not sure how this would work with EnterpriseDB's stack builder, but you
shouldbe able to pull the latest source when released and compile manually(?)</font></tt><br /><br /><tt><font
size="2">Regards</font></tt><br/><br /><tt><font size="2">Martin French.</font></tt><font
face="sans-serif">=============================================Romax Technology Limited Rutherford House Nottingham
Science& Technology Park Nottingham, NG7 2PZ England Telephone numbers: +44 (0)115 951 88 00 (main) For other
officelocations see: http://www.romaxtech.com/Contact ================================= =============== E-mail:
info@romaxtech.comWebsite: www.romaxtech.com ================================= ================ Confidentiality
StatementThis transmission is for the addressee only and contains information that is confidential and privileged.
Unlessyou are the named addressee, or authorised to receive it on behalf of the addressee you may not copy or use it,
ordisclose it to anyone else. If you have received this transmission in error please delete from your system and
contactthe sender. Thank you for your cooperation. =================================================</font> 

pgadmin-support by date:

Previous
From: Evan Martin
Date:
Subject: Query output is misleading due to grid cell size
Next
From: "Gary Clarke (M4 Systems Ltd)"
Date:
Subject: pg admin 92 beta 3 - bug report - row number 19 is out of range 0..18