X-Original-To: pgsql-admin-postgresql.org@postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id 6FE4F9FB27A for ; Fri, 28 Jul 2006 18:20:05 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 89094-09-2 for ; Fri, 28 Jul 2006 18:19:55 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey- Received: from web60417.mail.yahoo.com (web60417.mail.yahoo.com [209.73.178.145]) by postgresql.org (Postfix) with SMTP id 3E8E99FB285 for ; Fri, 28 Jul 2006 18:19:49 -0300 (ADT) Received: (qmail 26292 invoked by uid 60001); 28 Jul 2006 21:19:46 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=tXv+ioewBIBjxLkmoFkXxa5o+2tNqDN0WGMuTszLw2asEI7kGIp+RpqSvXXkxwK5Oe3pfa921Kmi5/lAYzV2b+OKoa2MdvLouWQ1cbgKDp/snVkbL7nVyLLeXtGmJEc69nJ+YpYhtPPLXyWygDJNYAj81ztS76sujZG9auWO6ac= ; Message-ID: <20060728211946.26290.qmail@web60417.mail.yahoo.com> Received: from [128.249.216.224] by web60417.mail.yahoo.com via HTTP; Fri, 28 Jul 2006 14:19:46 PDT Date: Fri, 28 Jul 2006 14:19:46 -0700 (PDT) From: Mingzuo Shen Subject: Re: Read db files directly To: pgsql-admin@postgresql.org In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=3.039 tagged_above=0 required=5 tests=AWL, DNS_FROM_RFC_ABUSE, DNS_FROM_RFC_POST, DNS_FROM_RFC_WHOIS X-Spam-Level: *** X-Archive-Number: 200607/274 X-Sequence-Number: 22520 Thanks Jeff! No, cannot do that. Because the folder has only the "oid" files. Don't know that to call them. All file names are numbers. Except the three following: pg_internal.init pgsql_tmp (empty folder) PG_VERSION /seagate400/1061329089 is the actual location of those 50 GB worth of files. I have a symlink like so: /var/lib/pgsql/data/base/1061329089 -> /seagate400/1061329089 Restarted many times. --- Jeff Frost wrote: > So what are the two locations in question? Is one > /var/lib/pgsql/data and > another one /usr/local/pgsql/data by chance? > > You can start another instance of postmaster in that > directory by using: > > pg_ctl -D start > > example: > > pg_ctl -D /usr/local/pgsql/data start > > If you do a ps -ef | grep data, you should probably > see something like: > > postgres 20991 1 4 13:33 pts/13 00:00:00 > /usr/bin/postmaster -p 5432 -D > /var/lib/pgsql/data > > which would tell you that the current instance of > postgres is running in > /var/lib/pgsql/data and you need to start the other > one up to see what's in > the other location. > > On Fri, 28 Jul 2006, Mingzuo Shen wrote: > > > Thanks Scott. > > That is a much clearer way of putting it. > > That old PostgreSQL runs just fine, > > in one place, but I have 50 GB of files in > > another place. PostgreSQL is not reading it. > > How can I persuade this PostgreSQL, > > or any PostgeSQL, to read that 50 GB of files. > > Or any independent tool to read the files. > > > > Tom Lane mentioned "vacuum". > > If only I knew the database name, > > I could try "psql dbname". > > But I don't know the database name either. > > I did run "vacuum" in my new testdb. > > > > Yeah. I guess the previous DBA put those files > > on a different file system, > > and then forgot about them, probably with > > good reason. But as I said, the previous DBA > > is no longer available. > > > > Imagine I send just those files to you, > > and you try to get some text out of them. > > I do not have the SQL used to create > > the tables, no table structures. > > > > > > > > --- Scott Marlowe > wrote: > > > >> It sounds like the current postgresql is running > in > >> one directory, and > >> you're looking in another directory. If you can > see > >> how postgresql was > >> started, does it have a -D switch that shows the > >> directory? My guess is > >> you could chmod 000 the master directory you're > >> looking at right now and > >> postgresql could still startup, because it's not > >> where you think it is. > > > > > > ---------------------------(end of > broadcast)--------------------------- > > TIP 3: Have you checked our extensive FAQ? > > > > http://www.postgresql.org/docs/faq > > > > > > -- > Jeff Frost, Owner > Frost Consulting, LLC > http://www.frostconsultingllc.com/ > Phone: 650-780-7908 FAX: 650-649-1954 >