Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id CBBA764FCCA for ; Thu, 18 Sep 2008 08:57:33 -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 77261-06 for ; Thu, 18 Sep 2008 08:57:31 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from mail-gx0-f17.google.com (mail-gx0-f17.google.com [209.85.217.17]) by postgresql.org (Postfix) with ESMTP id 19A6E64FCBF for ; Thu, 18 Sep 2008 08:57:30 -0300 (ADT) Received: by gxk10 with SMTP id 10so28883253gxk.19 for ; Thu, 18 Sep 2008 04:57:29 -0700 (PDT) Received: by 10.151.156.12 with SMTP id i12mr1125890ybo.194.1221739049578; Thu, 18 Sep 2008 04:57:29 -0700 (PDT) Received: by 10.150.156.1 with HTTP; Thu, 18 Sep 2008 04:57:29 -0700 (PDT) Message-ID: <937d27e10809180457i617487eydb8cf54e463792c6@mail.gmail.com> Date: Thu, 18 Sep 2008 12:57:29 +0100 From: "Dave Page" To: "Chander Ganesan" Subject: Re: Download links Cc: "Tom Lane" , "Andrew Sullivan" , pgsql-www@postgresql.org In-Reply-To: <48D240AF.8050204@otg-nc.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <937d27e10808110203l790a9c3eud97fdde42f70b92f@mail.gmail.com> <48CD0F6E.1060401@otg-nc.com> <20080915150524.GG5607@commandprompt.com> <48D17A38.1000208@otg-nc.com> <29492.1221689108@sss.pgh.pa.us> <48D181EC.3040204@otg-nc.com> <937d27e10809180039x710a1229ja28c81cb9b199db3@mail.gmail.com> <48D23B7E.5080104@otg-nc.com> <937d27e10809180442r75e34951uc091a28135c9e465@mail.gmail.com> <48D240AF.8050204@otg-nc.com> 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: 200809/118 X-Sequence-Number: 15827 On Thu, Sep 18, 2008 at 12:51 PM, Chander Ganesan wrote: > It's unfortunate that I only get to check my archive for this list > occasionally, otherwise I likely would have chimed in then. I understand > that it might be too late to make such changes... I'm just wondering if > that makes things more difficult for newer users in the long term, who might > be able to actually get upgrades to their DB without having to go through a > complex process (I'm not sure how the one-clicks are upgraded, but I assume > they cannot just do the package manager type upgrade). This probably won't > be a real "issue" until some kind of PostgreSQL DoS, Worm, or other attack > emerges, where they find themselves without a clean upgrade method (unless > they learn more PG stuff...). They just run the latest version of the installer to upgrade - it takes even fewer clicks than the initial install (about 4 iirc). I'm building them as part of the postgresql.org release process, so there will be no delays in getting new builds. Also, please note that on OS X, the 'one-click' installer *is* the platform standard. On there, it's MacPorts and Fink that are the alternate technologies. > > Out of curiosity, do the one-click installers also have one-click > uninstallers? That would be my other concern... Yes. -- Dave Page EnterpriseDB UK: http://www.enterprisedb.com