No doubt about this, there are a lot of features which are way more
important, but this was not the point at all.
The question was if there is any advantage of having it in the DB, and
the answer is: yes there is some advantage. It's a totally different
problem how important it is - there are many ways to handle scheduled
processes.
I would myself vote with leaving it out in favor of other features (my
favorit is shared row level locks, or anything else it would take to
finally solve the too strong lock for FK check problem, which makes
inserts in tables with FKs deadlock prone). Not that I could influence
at all the development through contributions, nor funding...
Cheers,
Csaba.
On Thu, 2004-12-16 at 14:58, Geoffrey wrote:
> Bruno Wolff III wrote:
>
> > cron isn't really part of the OS. Up until 8.0, any OS that Postgres
> > ran on had cron. I have seen claims that there is a version of cron that
> > runs under windows, but haven't verified that. Given this I don't see
> > how a dependence on cron is going to cause you portability problems.
>
> I would prefer the development effort be applied to more specific
> database engine issues and enhancements. As Bruno has noted, you can
> get some variation of cron on virtually every OS that runs Postgresql.
