| From: | Dave Page <dpage(at)pgadmin(dot)org> |
|---|---|
| To: | Paragon Corporation <lr(at)pcorp(dot)us> |
| Cc: | pgAdmin Support <pgadmin-support(at)postgresql(dot)org> |
| Subject: | Re: PgAgent 3.3.0 batch scripts on windows always get status failed |
| Date: | 2014-02-10 11:37:02 |
| Message-ID: | CA+OCxoyhXsMoyf4yeHOgwHHxMo3PeBvLozr=CUY3M8MYwTQBMw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-support |
On Mon, Feb 10, 2014 at 4:58 AM, Paragon Corporation <lr(at)pcorp(dot)us> wrote:
> We're having the same issue as described in this post.
>
> http://www.postgresql.org/message-id/CA+OCxoxoCGc7d7tRdyC5-32dDMtXyT1m59s_Lk
> 3moHTXxfMvmw(at)mail(dot)gmail(dot)com
>
>
> It sounds from the post that this issue was fixed. Was this change ever
> pushed to stack builder?
>
> I was thinking maybe it wasn't since the latest source release of pgAdmin
>
> http://www.postgresql.org/ftp/pgadmin3/release/pgagent/
>
> Is before this change was put into place and the pgAgent.exe packaged with
> stackbuilder reads File version 3.3.0.0, Product Version 3.3.0
No, there hasn't been a release of pgAgent since this fix was committed.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Page | 2014-02-10 14:30:11 | Re: pgAdmin 1.18.0 + slony-I 2.2.0 + PG 9.3 |
| Previous Message | Paragon Corporation | 2014-02-10 04:58:57 | Re: PgAgent 3.3.0 batch scripts on windows always get status failed |