No, because pgadmin treats it as a system catalog. You'll need to use ALTER TABLE in the query tool.
On 5/6/08, Benjamin Krajmalnik <[EMAIL PROTECTED]> wrote: > 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:[EMAIL PROTECTED] > > Sent: Tuesday, May 06, 2008 4:57 AM > > To: Benjamin Krajmalnik > > Cc: pgadmin-support@postgresql.org > > Subject: Re: [pgadmin-support] Potential issue with pgAgent > > when updating pga_jobsteplog > > > > On Mon, May 5, 2008 at 4:57 PM, Benjamin Krajmalnik > > <[EMAIL PROTECTED]> 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 > > > -- Dave Page EnterpriseDB UK: http://www.enterprisedb.com -- Sent via pgadmin-support mailing list (pgadmin-support@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgadmin-support
