On Tue, May 6, 2008 at 11:11 PM, Benjamin Krajmalnik <[EMAIL PROTECTED]> 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
>
> > -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
> > wh
g
> 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.
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
> stor
I have a scehduled job which randomizes a column inside a table.
The query is as follows:
update tbllocations set randsort=random();
Every time the job runs, it performs its task properly without any
issues, but I kept seeing the job as failed, and if you view the
statistics on the jon it shous
