Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 1731C64FCDE for ; Tue, 19 Aug 2008 05:14:49 -0300 (ADT) Received: from postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 03936-01-6 for ; Tue, 19 Aug 2008 05:14:24 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from svr2.hagander.net (svr2.hagander.net [88.198.128.226]) by postgresql.org (Postfix) with ESMTP id EF7516500AC for ; Tue, 19 Aug 2008 05:09:44 -0300 (ADT) Received: from dynamic.hagander.net ([127.0.0.1]) (encrypted and authenticated) by svr2.hagander.net (Postfix) with ESMTP id 021F7DCC906; Tue, 19 Aug 2008 10:09:43 +0200 (CEST) Received: from [127.0.0.1] (localhost [127.0.0.1]) by mha-laptop.hagander.net (Postfix) with ESMTP id 3BCA7124246; Tue, 19 Aug 2008 10:09:42 +0200 (CEST) Message-ID: <48AA7FC5.6070800@hagander.net> Date: Tue, 19 Aug 2008 10:09:41 +0200 From: Magnus Hagander User-Agent: Thunderbird 2.0.0.16 (X11/20080724) MIME-Version: 1.0 To: Alvaro Herrera CC: Tom Lane , Gregory Stark , Greg Smith , Michael Nacos , pgsql-hackers@postgresql.org Subject: Re: Overhauling GUCS References: <7473.1212625397@sss.pgh.pa.us> <200807161530.m6GFUNY28751@momjian.us> <407fa4640808130738s3537ca45j22322a5eb70f9173@mail.gmail.com> <407fa4640808180426q26a41cv817deb91dbbcd312@mail.gmail.com> <87y72u178j.fsf@oxford.xeocode.com> <3447.1219088424@sss.pgh.pa.us> <20080818215010.GC4454@alvh.no-ip.org> In-Reply-To: <20080818215010.GC4454@alvh.no-ip.org> X-Enigmail-Version: 0.95.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none X-Spam-Level: X-Archive-Number: 200808/802 X-Sequence-Number: 122556 Alvaro Herrera wrote: > Tom Lane escribió: >> Gregory Stark 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