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 9352352987 for ; Wed, 29 Jun 2005 15:20:10 -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 04077-02 for ; Wed, 29 Jun 2005 18:20:04 +0000 (GMT) Received: from smtp2.int-evry.fr (smtp2.int-evry.fr [157.159.10.45]) by svr1.postgresql.org (Postfix) with ESMTP id 4606A52863 for ; Wed, 29 Jun 2005 15:20:00 -0300 (ADT) Received: from [157.159.50.197] (calaz.int-evry.fr [157.159.50.197]) by smtp2.int-evry.fr (Postfix) with ESMTP id CD0F880C2 for ; Wed, 29 Jun 2005 20:19:51 +0200 (CEST) Message-ID: <42C2E656.6010403@free.fr> Date: Wed, 29 Jun 2005 20:20:06 +0200 From: jehan procaccia User-Agent: Mozilla Thunderbird 1.0.2-6 (X11/20050513) X-Accept-Language: en-us, en MIME-Version: 1.0 To: pgsql-admin@postgresql.org Subject: restore database from bare files Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-INT-MailScanner-Information: Please contact the ISP for more information X-INT-MailScanner: Found to be clean X-INT-MailScanner-SpamCheck: X-MailScanner-From: jehan.procaccia@free.fr X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests= X-Spam-Level: X-Archive-Number: 200506/276 X-Sequence-Number: 18031 hello, I crashed my server, and I didn't took the precaution to pg_dump one of my database :-( However I do have a tar file of the filesystem , it was on a RHEL 3 with rh-postgresql-server-7.3.9-2 and I have a tar of /var/lib/pgslq will just restoring the whole directory /var/lib/pgsql will suffices ? or should I do some tricky operations ? Here's what I have for example ..., how do I match a database name to the number -> here 16975 is which database ?: drwx------ / 0 2005-03-08 17:38:24 pgsql/data/base/16975/ -rw------- / 475136 2005-03-08 17:38:24 pgsql/data/base/16975/1255 -rw------- / 32768 2005-03-08 17:38:24 pgsql/data/base/16975/1247 and -rw------- / 0 2005-03-08 17:38:22 pgsql/data/global/16675 and drwx------ / 0 2005-05-31 18:14:51 pgsql/data/pg_xlog/ -rw------- / 16777216 2005-05-31 18:08:53 pgsql/data/pg_xlog/0000000000000011 -rw------- / 16777216 2005-06-28 15:33:10 pgsql/data/pg_xlog/0000000000000010 drwx------ / 0 2005-06-20 14:54:12 pgsql/data/pg_clog/ -rw------- / 262144 2005-06-01 18:15:07 pgsql/data/pg_clog/0000 -rw------- / 262144 2005-06-20 14:49:10 pgsql/data/pg_clog/0001 -rw------- / 32768 2005-06-28 15:10:19 pgsql/data/pg_clog/0002 and config files -rw------- / 3080 2005-04-22 18:33:17 pgsql/data/pg_hba.conf -rw------- / 1441 2005-03-08 17:38:22 pgsql/data/pg_ident.conf -rw------- / 5331 2005-03-25 15:19:47 pgsql/data/postgresql.conf -rw------- / 59 2005-06-28 15:27:14 pgsql/data/postmaster.opts The crashed happened during an upgrade to RHEL 4 , so now on RHEL postgresql version will be postgresql-server-7.4.7-2.RHEL4.1 ! any incompatibility or migration from 7.3.9-2 ? thanks.