Re: PgAdmin 3.5(latest) cannot edit PgAgent's schedules.

From: Eugene Wang <eugenewangfw(at)gmail(dot)com>
To: ashesh(dot)vashi(at)enterprisedb(dot)com, pgAdmin Support <pgadmin-support(at)postgresql(dot)org>
Subject: Re: PgAdmin 3.5(latest) cannot edit PgAgent's schedules.
Date: 2018-11-13 16:52:37
Message-ID: CAEsxC1bUBn3wHCnLgwALvt0-3Bj3YYUjV7-ivNjj=iPVxXTQGw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(dot)vashi(at)enterprisedb(dot)com>
wrote:

> Hi Eugene,
>
> Would you please share the version of pgAdmin 4?
>
> --
>
> Thanks & Regards,
>
> Ashesh Vashi
> EnterpriseDB INDIA: Enterprise PostgreSQL Company
> <http://www.enterprisedb.com>
>
>
> *http://www.linkedin.com/in/asheshvashi*
> <http://www.linkedin.com/in/asheshvashi>
>
>
> On Tue, Nov 13, 2018 at 9:26 PM Eugene Wang <eugenewangfw(at)gmail(dot)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,
>> -- Minutes
>>
>> ARRAY[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[],
>> -- Hours
>>
>> ARRAY[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 days
>> ARRAY[false,false,false,false,false,false,false]::boolean[],
>> -- Month days
>>
>> ARRAY[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[],
>> -- Months
>>
>> ARRAY[false,false,false,false,false,false,false,false,false,false,true,false]::boolean[]
>> ) RETURNING jscid INTO scid;
>>
>> Eugene
>>
>>
>> On Tue, Nov 13, 2018 at 10:45 AM Eugene Wang <eugenewangfw(at)gmail(dot)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_schedule
>>> SET
>>> jscstart='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,
>>>
>>> Eugene
>>>
>>>
>>> Yujie Wang (Welcome to call me Eugene, for your pronunciation
>>> convenience)
>>> GIS Developer
>>> Connected2fiber
>>> Linkedin : https://www.linkedin.com/in/yujie-wang-61a129a0/
>>>
>>

In response to

Browse pgadmin-support by date

  From Date Subject
Next Message Eugene Wang 2018-11-13 21:54:22 Re: PgAgent daemon terminated itself when it was running a time-consuming job.
Previous Message Ashesh Vashi 2018-11-13 16:32:10 Re: PgAdmin 3.5(latest) cannot edit PgAgent's schedules.