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 9258252923 for ; Thu, 23 Jun 2005 05:11:23 -0300 (ADT) 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 78868-04 for ; Thu, 23 Jun 2005 08:11:20 +0000 (GMT) Received: from as1.cineca.com (as1.cineca.com [130.186.84.251]) by svr1.postgresql.org (Postfix) with ESMTP id EEA1A5296E for ; Thu, 23 Jun 2005 05:11:18 -0300 (ADT) Received: from localhost (localhost.localdomain [127.0.0.1]) by as1.cineca.com (Postfix) with ESMTP id E1A926598A for ; Thu, 23 Jun 2005 08:11:18 +0000 (UTC) Received: from cineca.mm.cineca.it (cineca.mm.cineca.it [130.186.10.200]) by as1.cineca.com (Postfix) with ESMTP id 23A4B6598E for ; Thu, 23 Jun 2005 08:11:17 +0000 (UTC) Received: from [130.186.7.197] (dhcp7-197.cineca.it [130.186.7.197]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) as user f.dallaca@cineca.it by cineca.mm.cineca.it (Postfix) with ESMTP id DC12E4F6488 for ; Thu, 23 Jun 2005 10:11:16 +0200 (MEST) Message-ID: <42BA6EA4.1070806@cineca.it> From: Francesco Dalla Ca' Organization: CINECA User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050513 Fedora/1.7.8-1.3.1 X-Accept-Language: en-us, en MIME-Version: 1.0 To: pgsql-admin@postgresql.org Subject: pg 8.0: Restoring the catalog after disk corruption: it's possible? Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Date: Thu, 23 Jun 2005 10:11:16 +0200 (MEST) X-Virus-Scanned: Cineca AppOs 0.85 at as1.cineca.com X-Virus-Scanned: by amavisd-new at hub.org X-Archive-Number: 200506/165 X-Sequence-Number: 17920 With Pg 8.0.x, with the capability of tablespace, it's possible to create a Database that relie on many tbs. Scenario: I create the catalog (schemes pg_catalog, information_schema, obviously except the tables/view that relies in tbs "pg_global") on the tablespace "tbs1" and all other user objects on a different tbs "tbs2". tbs1 and tbs2 stand on different volumes (v1 and v2). After a v1 crash and subsequent tbs1 and catalog lost, there are some ways (scripts?) to restore the catalog on a freshly new "tbs1"? (without creating a DB and restarting from the last backup?). Best regards. -- =========================================== CINECA Via Magnanelli 6/3 40033 Casalecchio di Reno (Bologna) Settore Gestione Sistemi Francesco Dalla Ca' Email f.dallaca@cineca.it ===========================================