Re: PgAdmin 3.5(latest) cannot edit PgAgent's schedules. - Mailing list pgadmin-support
From | Eugene Wang |
---|---|
Subject | Re: PgAdmin 3.5(latest) cannot edit PgAgent's schedules. |
Date | |
Msg-id | CAEsxC1bUBn3wHCnLgwALvt0-3Bj3YYUjV7-ivNjj=iPVxXTQGw@mail.gmail.com Whole thread Raw |
In response to | Re: PgAdmin 3.5(latest) cannot edit PgAgent's schedules. (Ashesh Vashi <ashesh.vashi@enterprisedb.com>) |
List | pgadmin-support |
My apologies! I meant to say PgAgent 4.5 and that is why I mentioned (latest).
Thank you very much for notifying me about this.
Best regards,
On Tue, Nov 13, 2018 at 11:32 AM Ashesh Vashi <ashesh.vashi@enterprisedb.com> wrote:
Hi Eugene,Would you please share the version of pgAdmin 4?On Tue, Nov 13, 2018 at 9:26 PM Eugene Wang <eugenewangfw@gmail.com> wrote:An update:Errors not only happened on changing time schedules, but also happened on creating schedules now.Since I cannot edit the time schedule, I tried to removed and create a new schedule for the existed job. I successfully removed the old schedule and got an error message like below:ERROR: syntax error at or near "INTO"
LINE 19: ) RETURNING jscid INTO scid;
^Here comes the interpreted SQL codes. The error happened at the very last line: ```) RETURNING jscid INTO scid;``` .-- Inserting a schedule (jobid: 6)INSERT INTO pgagent.pga_schedule(jscjobid, jscname, jscdesc, jscenabled,jscstart, jscminutes, jschours, jscweekdays, jscmonthdays, jscmonths) VALUES (6, 'onetime test'::text, ''::text, true,'2018-11-13 10:47:36 -05:00'::timestamp with time zone,-- MinutesARRAY[false,false,false,false,false,false,false,false,false,false,false,false,false,false,false,false,false,false,false,false,false,false,false,false,false,false,false,false,false,false,false,false,false,false,false,false,false,false,false,false,false,false,false,false,false,false,false,false,false,false,true,false,false,false,false,false,false,false,false,false]::boolean[],-- HoursARRAY[false,false,false,false,false,false,false,false,false,false,false,false,false,false,false,true,false,false,false,false,false,false,false,false]::boolean[],-- Week daysARRAY[false,false,false,false,false,false,false]::boolean[],-- Month daysARRAY[false,false,false,false,false,false,false,false,false,false,false,false,true,false,false,false,false,false,false,false,false,false,false,false,false,false,false,false,false,false,false,false]::boolean[],-- MonthsARRAY[false,false,false,false,false,false,false,false,false,false,true,false]::boolean[]) RETURNING jscid INTO scid;EugeneOn Tue, Nov 13, 2018 at 10:45 AM Eugene Wang <eugenewangfw@gmail.com> wrote:Hi Pgadmin team,When I was trying to edit the time schedule of a PgAgent job, I got an error message like below:ERROR: malformed array literal: "[false,false,false,false,false,false,false,false,false,false,true,false]"
LINE 7: jscmonths='[false,false,false,false,false,false,false,fa...
^
DETAIL: "[" must introduce explicitly-specified array dimensions.In the SQL tab, I noticed that PgAdmin interpreted my changes as below in SQL.-- Updating the schedule (id: 8, jobid: 6)UPDATE pgagent.pga_scheduleSETjscstart='2018-08-26T22:04:42-04:00'::timestamptz,jscmonths='[false,false,false,false,false,false,false,false,false,false,true,false]'::boolean[],jscminutes='[false,false,false,false,false,false,false,false,false,false,false,false,false,false,false,false,false,false,false,false,false,false,false,false,false,false,false,false,false,false,false,false,false,false,false,false,false,true,false,false,false,false,false,false,false,false,false,false,false,false,false,false,false,false,false,false,false,false,false,false]'::boolean[],jscmonthdays='[false,false,false,false,false,false,false,false,false,false,false,false,true,false,false,false,false,false,false,false,false,false,false,false,false,false,false,false,false,false,false,false]'::boolean[],jschours='[false,false,false,false,false,false,false,false,false,false,false,false,false,false,false,true,false,false,false,false,false,false,false,false]'::boolean[]WHERE jscid=8::integer AND jscjobid=6::integer;I think someone could look at it. Thank you very much in advance.Best,EugeneYujie Wang (Welcome to call me Eugene, for your pronunciation convenience)GIS DeveloperConnected2fiber
pgadmin-support by date: