From: | Dave Page <dpage(at)pgadmin(dot)org> |
---|---|
To: | Kurics János <kurics40(at)freemail(dot)hu> |
Cc: | pgAdmin Support <pgadmin-support(at)postgresql(dot)org> |
Subject: | Re: pgagent on Greenplum |
Date: | 2013-05-13 16:06:35 |
Message-ID: | CA+OCxoy45WsoeoD4s1fYS7+BrWyfUxs=YCuMkArtv4Z-dZevWA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-support |
On Mon, May 13, 2013 at 4:55 PM, Kurics János <kurics40(at)freemail(dot)hu> wrote:
>
> Hello all,
>
> Could someone make pgagent on Greenplum work?
>
> Env info:
> Linux gp 2.6.32-358.2.1.el6.x86_64 #1 SMP Wed Mar 13 00:26:49 UTC 2013
> x86_64 x86_64 x86_64 GNU/Linux
> pgAgent-3.3.0-Source.tar.gz
> greenplum-db-4.2.2.4-build-1-CE-RHEL5-x86_64.bin
> pgadmin3-1.16.1.zip
>
> I could install, start daemon and see it in pgAdmin client but I can not
> schedule a job.
>
> Error message:
> function cannot execute on segment because it issues a non-SELECT statement
> (fucntion.c133) (seg0 localhost.localdomain:40000 pid=2780 (cdbisp.c1475)
> DETAIL SQL statement "UPDATE pgagent.pga_job SET jobnextrun = NULL WHERE
> jobenalbed AND jobid=$1"
>
> PL/pgSQL function "pga_schedule_trigger" line 10 at SQL statement
>
> So GP doesn't support triggers however I could create them.
If that's the case, then it'll never work I'm afraid. Use of triggers
is fundamental to the way pgAgent works.
--
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 | 2013-05-14 18:09:26 | Re: 1.16.1: many operations cause display tree to collapse |
Previous Message | Kurics János | 2013-05-13 15:55:01 | pgagent on Greenplum |