Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: Potential issue with pgAgent when updating pga_jobsteplog
- From: "Dave Page" <dpage(at)pgadmin(dot)org>
- To: "Benjamin Krajmalnik" <kraj(at)illumen(dot)com>, "PgAdmin Support" <pgadmin-support(at)postgresql(dot)org>
- Subject: Re: Potential issue with pgAgent when updating pga_jobsteplog
- Date: Wed, 7 May 2008 08:05:07 +0100
- Message-id: <937d27e10805070005x71c6b358x8cb5eb0d479c2f81(at)mail(dot)gmail(dot)com>
On Tue, May 6, 2008 at 11:11 PM, Benjamin Krajmalnik <kraj(at)illumen(dot)com> wrote: > What query should I issue to change this. Not sure since it is a system > catalog. It's not really a catalog - it's only pgAdmin that treats it as one. Something like this (untested) should do: ALTER TABLE pgagent.pga_jobsteplog ALTER COLUMN jslresult TYPE int4; -- Dave Page EnterpriseDB UK: http://www.enterprisedb.com
- References:
- Potential issue with pgAgent when updating pga_jobsteplog
- From: Benjamin Krajmalnik
- Re: Potential issue with pgAgent when updating pga_jobsteplog
- From: Dave Page
- Re: Potential issue with pgAgent when updating pga_jobsteplog
- From: Benjamin Krajmalnik
- Re: Potential issue with pgAgent when updating pga_jobsteplog
- From: dpage
- Potential issue with pgAgent when updating pga_jobsteplog
- Prev by Date: Re: Editing Views with EditGrid
- Next by Date: Re: Editing Views with EditGrid
- Previous by thread: Re: Potential issue with pgAgent when updating pga_jobsteplog
- Next by thread: Editing Views with EditGrid
- Indexes: