Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id CE6E1650E90 for ; Tue, 1 Jul 2008 16:54:40 -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 93534-02 for ; Tue, 1 Jul 2008 16:54:34 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.180]) by postgresql.org (Postfix) with ESMTP id E8A7A64FD64 for ; Tue, 1 Jul 2008 16:54:36 -0300 (ADT) Received: by py-out-1112.google.com with SMTP id d37so35901pye.29 for ; Tue, 01 Jul 2008 12:54:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=kSH22ixdtOc44pF+jKBCWIlzNg7tpyf7rkV1pcuU32Y=; b=m1TfJ9DzdzBSZ90mDeE1nj8KfX/+vCto7YSiRc3Oqv3dHUjxZV/+tMhHv6c+87lGCM ab/3LHBad5zZiRoGLlA1gu4OzS5CoIXGrGJvl3Sz/kcFTa49QWMRNLbrq8/4UzGAKVQ5 iCJeeS1xlJnweFOm820hN3xUtbOy6Rhlu8R3E= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=VqL+G2Ny9RyuzPvl0UQCw350VZmEGZAQelVb5lpWKC0ymGD8CvO8Klds23ts68i48Y TfdLTIryd/oly98d4UZ0OulO7mA+75yYRLs4qFqtTPX6KyKnPvPcf1iba1NNNcZPg3Bc 7rIb6XyLk5+KiL8r3Uftcb7GQpXsxKixQBvpI= Received: by 10.114.110.1 with SMTP id i1mr6227031wac.112.1214942075161; Tue, 01 Jul 2008 12:54:35 -0700 (PDT) Received: by 10.114.180.17 with HTTP; Tue, 1 Jul 2008 12:54:35 -0700 (PDT) Message-ID: Date: Tue, 1 Jul 2008 13:54:35 -0600 From: "Scott Marlowe" To: Decibel! Subject: Re: After upgrade cleanup Cc: "Carol Walter" , pgsql-admin@postgresql.org In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200807/16 X-Sequence-Number: 29626 On Fri, Jun 20, 2008 at 3:19 PM, Decibel! wrote: > On Jun 19, 2008, at 8:13 AM, Carol Walter wrote: >> >> I just did an upgrade from 8.1 to 8.2.3. We'll go up to 8.3.3 very soon, >> but for reasons I won't go into, this intermediate step was necessary. My >> problem is, now that the upgrade is done, how can I clean up the database >> from the old version. I leave the original database up as long as I can >> when I do an upgrade just in case I need to revert to it. Now I have the >> databases from two versions on my server and I need to get rid of the old >> one. Can I just remove the old files from the data directories? With other >> systems, I've had trouble removing database files because upgrades use >> certain files from old versions. I don't want to break my new database. >> I'm on Solaris 10. > > > Not only does the new version not use files from the old, it doesn't even > know it exists. You can just nuke all the 8.1 stuff. If you're paranoid, then you can also do: sudo chmod 000 /old/data/dir and see if anything breaks.