Alvaro Herrera wrote:
> Tom Lane escribió:
>> Gregory Stark <stark@enterprisedb.com> writes:
>>> The entire target market for such a thing is DBAs stuck on hosted databases
>>> which don't have shell access to their machines. Perhaps the overlap between
>>> that and the people who can write a server-side module which dumps out a
>>> config file according to some rules is just too small?
>> There's a veritable boatload of stuff we do that assumes shell access
>> (how many times have you seen cron jobs recommended, for instance?).
>> So I'm unconvinced that "modify the config without shell access"
>> is really a goal that is worth lots of effort.
>
> Actually, lots of people are discouraged by suggestions of using cron to
> do anything. The only reason cron is suggested is because we don't have
> any other answer, and for many people it's a half-solution. An
> integrated task scheduler in Pg would be more than welcome.
Yes, I hear a lot of people complaining aobut that too. Now that we have
a working autovacuum, some of it goes away though - no need to cron your
VACUUMs in most cases anymore. But there are still backups - but they
are often managed by the scheduler of an enterprise backup software.
> Also, remember that pgAdmin already comes with a pgAgent thing.
Yeah, it's a real life-saver on Windows where the builtin task-scheduler
isn't as readily accessible or easy to use..
//Magnus
