Date: Mon, 18 Aug 2008 17:50:10 -0400
From: Alvaro Herrera <alvherre@commandprompt.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Gregory Stark <stark@enterprisedb.com>, Greg Smith <gsmith@gregsmith.com>,
	Michael Nacos <m.nacos@gmail.com>, pgsql-hackers@postgresql.org
Subject: Re: Overhauling GUCS
Message-ID: <20080818215010.GC4454@alvh.no-ip.org>
References: <7473.1212625397@sss.pgh.pa.us>
	<200807161530.m6GFUNY28751@momjian.us>
	<407fa4640808130738s3537ca45j22322a5eb70f9173@mail.gmail.com>
	<Pine.GSO.4.64.0808171610220.22642@westnet.com>
	<407fa4640808180426q26a41cv817deb91dbbcd312@mail.gmail.com>
	<Pine.GSO.4.64.0808181250190.17947@westnet.com>
	<87y72u178j.fsf@oxford.xeocode.com> <3447.1219088424@sss.pgh.pa.us>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <3447.1219088424@sss.pgh.pa.us>
User-Agent: Mutt/1.5.18 (2008-05-17)

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.

Also, remember that pgAdmin already comes with a pgAgent thing.

-- 
Alvaro Herrera                                http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support