Re: pgAgent - Log error when running

Поиск
Список
Период
Сортировка
От Dave Page
Тема Re: pgAgent - Log error when running
Дата
Msg-id E7F85A1B5FF8D44C8A1AF6885BC9A0E40154C3BA@ratbert.vale-housing.co.uk
обсуждение исходный текст
Ответ на Re: pgAgent - Log error when running  ("Chuck" <watsocd@gmail.com>)
Ответы Re: pgAgent - Log error when running  ("Chuck" <watsocd@gmail.com>)
Список pgadmin-support

> -----Original Message-----
> From: pgadmin-support-owner@postgresql.org
> [mailto:pgadmin-support-owner@postgresql.org] On Behalf Of Chuck
> Sent: 02 August 2006 13:19
> To: pgadmin-support@postgresql.org
> Subject: Re: [pgadmin-support] pgAgent - Log error when running
>
> Yes, it was a typo in the message but I entered and ran the command
> correctly.
>
> Some new information. I ran the command again but used a superuser
> account and added password=jjjj to the command line. My test script is
> being run by pgAgent every two minutes. It shoud be running every
> minute.
>
> I know this is not the suggested method for security reasons. Any idea
> what is wrong with the postgres account that woud not allow it to be
> used?

The postgres account normally is a superuser account. Assuming in this
case it isn't, does it have permission to access the pgagent schema and
the postgres database? And to connect from 127.0.0.1?

As for the two minute thing, the next runtime is determined at the end
of each run, so if the job duration is greater than 1 minute but less
than two then you will get 2 minute intervals. This prevents the server
dying under load of an ever-increasing number of overlapping instances
of the same job.

The other thing to check is the poll time (-t option). If you specify
that on the command line, make sure it's less than the minimum time
between job runs. The default is 10 seconds btw.

Regards, Dave.



В списке pgadmin-support по дате отправления:

Предыдущее
От: "Chuck"
Дата:
Сообщение: Re: pgAgent - Log error when running
Следующее
От: "Chuck"
Дата:
Сообщение: Re: pgAgent - Log error when running