From: | Dave Page <dpage(at)postgresql(dot)org> |
---|---|
To: | Luke Lonergan <llonergan(at)greenplum(dot)com> |
Cc: | pgadmin-support(at)postgresql(dot)org |
Subject: | Re: Small change needed to support Greenplum DB |
Date: | 2007-10-12 14:20:25 |
Message-ID: | 470F82A9.3030906@postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-support |
Luke Lonergan wrote:
> Hi all,
>
> A customer of ours is using pgAgent with Greenplum Database and needs a
> change to one of the queries used by pgAgent to allow it to work with
> Greenplum.
>
> Here is the conversation:
> _http://groups.google.com/group/pgsql.bugs/browse_thread/thread/27866354fa4d7a5e/60e6e5de3c5156d4#60e6e5de3c5156d4
>
> _The problem is that Greenplum does not support some correlated
> subqueries, so Jon created a version of the query that is both faster
> and does not use a correlated subquery.
>
> The requested change is from this in pgaJob.cpp:
Hi Luke,
Does Greenplum support DISTINCT ON? Specifically,
SELECT j.*, cl.*, ag.*, sub.jlgstatus
FROM pgagent.pga_job j JOIN
pgagent.pga_jobclass cl ON cl.jclid=jobjclid LEFT OUTER JOIN
pgagent.pga_jobagent ag ON ag.jagpid=jobagentid JOIN
(SELECT DISTINCT ON (jlgjobid) jlgstatus, jlgjobid
FROM pgagent.pga_joblog
ORDER BY jlgjobid, jlgid desc) sub ON sub.jlgjobid = j.jobid
-- + restriction +
ORDER BY jobname;
Regards, Dave.
From | Date | Subject | |
---|---|---|---|
Next Message | Rolf A. de By | 2007-10-12 14:24:08 | Bug report pgadmin 1.8.0 Beta 5 (Sep 10 2007, rev 6631) |
Previous Message | Ariel R. Giomi | 2007-10-12 13:01:56 | ALTER TABLE sample SET TABLESPACE |