Re: Potential issue with pgAgent when updating pga_jobsteplog

From: "Benjamin Krajmalnik" <kraj(at)illumen(dot)com>
To: "Dave Page" <dpage(at)pgadmin(dot)org>
Cc: <pgadmin-support(at)postgresql(dot)org>
Subject: Re: Potential issue with pgAgent when updating pga_jobsteplog
Date: 2008-05-06 18:53:05
Message-ID: F4E6A2751A2823418A21D4A160B689880E988F@fletch.stackdump.local
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-support

Via pgAdmin, going into the pgagent catalog, I do not have an option of
changing the column type to int4.

> -----Original Message-----
> From: Dave Page [mailto:dpage(at)pgadmin(dot)org]
> Sent: Tuesday, May 06, 2008 4:57 AM
> To: Benjamin Krajmalnik
> Cc: pgadmin-support(at)postgresql(dot)org
> Subject: Re: [pgadmin-support] Potential issue with pgAgent
> when updating pga_jobsteplog
>
> On Mon, May 5, 2008 at 4:57 PM, Benjamin Krajmalnik
> <kraj(at)illumen(dot)com> wrote:
> >
> > I believe one of 2 things probably needs to be done:
> >
> > 1. Update the documentation to mention what range the
> result needs to be.
> > This means that queries which affect many rows need to be
> encapsulated
> > in a stored procedure or have a supplementary query such as
> "select 1"
> > added to the step in order to return an in-range value 2. Change
> > jslresult to a data type which will accomodate a larger value.
>
> I've gone with the second option and increased the jslresult
> column to be an int4 (matching the C++ code). You should be
> able to increase the column size on your server as no other
> code changes are required.
>
> Thanks, Dave
>
> --
> Dave Page
> EnterpriseDB UK: http://www.enterprisedb.com
>

In response to

Responses

Browse pgadmin-support by date

  From Date Subject
Next Message dpage 2008-05-06 19:15:26 Re: Potential issue with pgAgent when updating pga_jobsteplog
Previous Message Dave Page 2008-05-06 13:33:57 Re: Editing Views with EditGrid