X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id E618C3A2B23 for ; Mon, 25 Oct 2004 15:18:12 +0100 (BST) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 02278-06 for ; Mon, 25 Oct 2004 14:18:03 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id 0B2823A403A for ; Mon, 25 Oct 2004 15:18:06 +0100 (BST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id i9PEI6vw018282; Mon, 25 Oct 2004 10:18:06 -0400 (EDT) To: Jodi Kanter Cc: Postgres Admin List Subject: Re: db rename In-reply-to: <417CF897.1020701@virginia.edu> References: <417CF897.1020701@virginia.edu> Comments: In-reply-to Jodi Kanter message dated "Mon, 25 Oct 2004 08:59:03 -0400" Date: Mon, 25 Oct 2004 10:18:06 -0400 Message-ID: <18281.1098713886@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200410/332 X-Sequence-Number: 15325 Jodi Kanter writes: > I thought there was an option to rename a database? No, but you could always do an UPDATE on pg_database. It might be a good idea to ensure there are no backends running in the target database when you do the update. (I think that recent releases wouldn't care particularly, but I'm less sure about 7.3.4.) regards, tom lane