Skip site navigation (1) Skip section navigation (2)

Re: Ideas for new features

From: Dave Page <dpage(at)pgadmin(dot)org>
To: Magnus Hagander <magnus(at)hagander(dot)net>
Cc: Guillaume Lelarge <guillaume(at)lelarge(dot)info>, pg <pg(at)kuhnsteffen(dot)de>, pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org>
Subject: Re: Ideas for new features
Date: 2010-08-23 09:18:53
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgadmin-hackers
On Mon, Aug 23, 2010 at 10:13 AM, Magnus Hagander <magnus(at)hagander(dot)net> wrote:
> On Mon, Aug 23, 2010 at 11:10, Dave Page <dpage(at)pgadmin(dot)org> wrote:
>> On Mon, Aug 23, 2010 at 9:47 AM, Guillaume Lelarge
>> <guillaume(at)lelarge(dot)info> wrote:
>>>> *Higher time resolution for pgAdmin jobs. A job should be runable e.g.
>>>> every 1 second or 10 seconds.
>>> +1 (ticket added, #228).
>> And closed it again. This is extremely unlikely to happen - it would
>> require significant code changes, would significantly increase load on
>> the server, and is of extremely limited use.
> I'll buy the significant code-changes, but I dont' see how it would
> necessarily increase the load on the server. Maybe because I don't
> know pgagent enough - can you explain how?

Jobs are stored in the database with a 'next run' time that is
recalculated from the schedules each time the job runs or is modified.
The agent polls the database for jobs that are at, or past their next
run time every minute by default. To reduce the resolution to 10
seconds or even 1 second, we'd need to start polling the database at
least every 10 or 1 second(s).

Dave Page
Twitter: @pgsnake

EnterpriseDB UK:
The Enterprise Postgres Company

In response to


pgadmin-hackers by date

Next:From: Magnus HaganderDate: 2010-08-23 09:22:27
Subject: Re: Ideas for new features
Previous:From: Magnus HaganderDate: 2010-08-23 09:13:53
Subject: Re: Ideas for new features

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group