From: | "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> |
---|---|
To: | "Glen Sasek" <sasekg(at)gmail(dot)com>, <pgadmin-hackers(at)postgresql(dot)org> |
Subject: | Re: pga_next_schedule function bug |
Date: | 2005-12-23 08:24:07 |
Message-ID: | E7F85A1B5FF8D44C8A1AF6885BC9A0E4E7EC43@ratbert.vale-housing.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
> -----Original Message-----
> From: pgadmin-hackers-owner(at)postgresql(dot)org
> [mailto:pgadmin-hackers-owner(at)postgresql(dot)org] On Behalf Of Glen Sasek
> Sent: 22 December 2005 23:24
> To: pgadmin-hackers(at)postgresql(dot)org
> Subject: [pgadmin-hackers] pga_next_schedule function bug
>
> When creating a schedule or running the test code in pgagent.sql the
> following occurs:
> ERROR: syntax error at or near "IF"
> CONTEXT: compile of PL/pgSQL function "pga_next_schedule"
> near line 161
> PL/pgSQL function "pga_job_trigger" line 4 at select into variables
> PL/pgSQL function "pga_schedule_trigger" line 10 at SQL statement
>
> This can be fixed by editing the pga_next_schedule function
> around lines
> 131-163; the problem is that there is no ELSEIF keyword in
> the language. The
> correct syntax is ELSIF.
Ahh, ELSEIF was added in 8.0 - didn't realise I'd used the new form.
I'll commit appropriate fixes ASAP.
Thanks for the report.
Regards, Dave.
From | Date | Subject | |
---|---|---|---|
Next Message | svn | 2005-12-23 08:30:47 | SVN Commit by dpage: r4852 - branches/REL-1_4_0_PATCHES/pgadmin3/xtra/pgagent |
Previous Message | Tom Lane | 2005-12-23 05:39:51 | Re: [pgadmin-hackers] Client-side password encryption |