Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hY54K-0004tn-SF for pgadmin-hackers@arkaria.postgresql.org; Tue, 04 Jun 2019 08:45:21 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1hY54J-0001pt-LX for pgadmin-hackers@arkaria.postgresql.org; Tue, 04 Jun 2019 08:45:19 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hY54J-0001np-5a for pgadmin-hackers@lists.postgresql.org; Tue, 04 Jun 2019 08:45:19 +0000 Received: from mail-ot1-x342.google.com ([2607:f8b0:4864:20::342]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hY54G-0002a8-88 for pgadmin-hackers@postgresql.org; Tue, 04 Jun 2019 08:45:17 +0000 Received: by mail-ot1-x342.google.com with SMTP id d17so4601288oth.5 for ; Tue, 04 Jun 2019 01:45:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=enterprisedb-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=fvlHO/MkK7pLLABKCvrkIQNk+VzRek0RrfqBBiMaGxg=; b=xtHz2hmjWVRWJ/z8syU+LEOk+NBfvA9HQicMssZ1lDT7m/S1Rcca9m9KArsENgjlOx hiOohaj7+k+VT6fNgi/T/mfuyFNO2xWE9Xp8krkuK3cmhwrEz5J9+z3KZ1j+tXxPMRt3 NeX01B7OoPjw0qbxzx8R1auG/LXoL4sAlxMXaj3kk4xXa/s6tHihlYASInXhjufIVnGs M1BOTBBYWLCmer4v96tvnOFsc/UhCNdRSD1QeAJ9ivtK0euuGDQjogOna+wABiBDrD1U yX9d3P63v3Wm+bNT+VyPaGYa7x/3bQ1tEDj8wF0ibJJowZYhwi4QPYrXzPARgRZYVNoY woaA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=fvlHO/MkK7pLLABKCvrkIQNk+VzRek0RrfqBBiMaGxg=; b=Z0xmWSWNbZCC6FkCfd+jG0W2Qc0ZWHkLsr2Bt6x3QoSHlfw5f0qGkN6uEw/co+mwqp TcewXUJ4nBUZnZHvxYjQMnQxzSKW+86fhRl1TFDRxvrs0E+JCvEUjYLfW9vVjSsOc4/C LSdf/tsjbhNsHO9G0fuhfFOEcyWwtLfK6ZYroIRnE9NKTiMWRg5Ybz6akr2W+HqJa3G0 wX9VddM1geFi/isi8UM+6nb732gFHPJXoI7n66vla5aff5szzqnxNNC+NsfGdzjyF8y/ 5MAQdw1wJ1Gk+J15nzcVARmih9g3plwU2W0EZyNu2bm1z3esiaUnp9tlr+7cORyGGVYa fyaQ== X-Gm-Message-State: APjAAAVeD5wmz/pUXuIVpUUlPRBODESjCl6pXzekmuc0nfsCVuPnggoB /+gQNSkLjTRImyC0MQqPdWxFsxNYElAdwm0hc7TBeg== X-Google-Smtp-Source: APXvYqw+e99ioh9I38AVUebiwrzNcxbOKrdNqU3NMf2WnzCd6vDSgDYbJXKyRofC8wf3OO7IwIINhWiTWxoXTFSTIe8= X-Received: by 2002:a9d:70da:: with SMTP id w26mr4123354otj.270.1559637915282; Tue, 04 Jun 2019 01:45:15 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Khushboo Vashi Date: Tue, 4 Jun 2019 14:15:05 +0530 Message-ID: Subject: Re: Help on pgAgent To: John G198 Cc: pgadmin-hackers Content-Type: multipart/alternative; boundary="000000000000eb47eb058a7b7f06" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --000000000000eb47eb058a7b7f06 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Tue, Jun 4, 2019 at 1:36 PM John G198 wrote: > Yes, I did. But it doesn't run neither, it does update the next run date > but doesn't actually do anything even the field last run still shows > nothing. I checked the SQL as I'm trying to update a table column and the > SQL is correct so I don't what is failing > > Please enable logging (Ref: https://www.pgadmin.org/faq/#8) and share the log file after running the job with Run now. > El lun., 3 de jun. de 2019 11:59 p. m., Khushboo Vashi < > khushboo.vashi@enterprisedb.com> escribi=C3=B3: > >> >> >> On Tue, Jun 4, 2019 at 1:46 AM John G198 >> wrote: >> >>> Hi im trying to use pgAgent on pgAdmin4 using Windows 10 and i cant see >>> why but it doesnt work, it doesnt run the jobs created and i just want = to >>> know if it has something to do with my postgreSQL version 11.2 maybe >>> pgAgent isnt compatible with this version. >>> So could you let me know whats going on? and what alternative do i >>> have?, i really need to use Scheduled jobs for this web page db project= i >>> have >>> >> >> Have you tried to run manually via *Run now* option in the context menu >> of the pgAgent job? >> > --000000000000eb47eb058a7b7f06 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


=
On Tue, Jun 4, 2019 at 1:36 PM John G= 198 <jonathandelatorre9= 8@gmail.com> wrote:
Yes, I did. But it doesn't run neither, it= does update the next run date but doesn't actually do anything even th= e field last run still shows nothing. I checked the SQL as I'm trying t= o update a table column and the SQL is correct so I don't what is faili= ng=C2=A0

Please enable logging (Ref:=C2=A0https://www.pgadmin.org/faq/#8)=C2= =A0 and share the log file after running the job with Run now.
<= div dir=3D"ltr" class=3D"gmail_attr">El lun., 3 de jun. de 2019 11:59 p. m.= , Khushboo Vashi <khushboo.vashi@enterprisedb.com> escribi=C3=B3:


On Tue, Jun 4, 2019 at 1:46 AM John G198 <jo= nathandelatorre98@gmail.com> wrote:
Hi im trying to use pgAgent on = pgAdmin4 using Windows 10 and i cant see why but it doesnt work, it doesnt = run the jobs created and i just want to know if it has something to do with= my postgreSQL version 11.2 maybe pgAgent isnt compatible with this version= .
So could you let me know whats going=C2=A0on? and what alternative do= i have?, i really need to use Scheduled jobs for this web page db project = i have

Have you tried to run ma= nually via Run now option in the context menu of the pgAgent job?
--000000000000eb47eb058a7b7f06--