From: Mingzuo Shen <mzshen@yahoo.com>
To: Scott Marlowe <smarlowe@g2switchworks.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Read db files directly
Date: Fri, 28 Jul 2006 12:43:01 -0700 (PDT)
Message-ID: <20060728194301.67345.qmail@web60416.mail.yahoo.com> (raw)
In-Reply-To: <1154115153.31664.129.camel@state.g2switchworks.com>
Thanks Scott.
Well, PostgreSQL runs just fine.
As I said, I can create new db, new tables, etc.
everything works just fine for new stuff.
when I say psql shows nothing,
I really mean "nothing".
No error messages.
Of course if I create a new db, psql -l shows my
new db.
psql -l
List of databases
Name | Owner | Encoding
--------+----------+-----------
testdb | postgres | SQL_ASCII
(1 row)
What I am curious about is, what are
in those 50 GB worth of files.
"strings" shows me there are some data that
I might be interested in saving before I erase
this pg instance.
--- Scott Marlowe <smarlowe@g2switchworks.com> wrote:
> Can you get postgresql to startup? Are you trying
> to use pg_ctl to
> start it or /etc/init.d/postgresql scripts?
>
> Basically, you need the database up and running
> first. When you "psql
> and pg_dump don't see those files" what errors are
> you actually getting?
>
> On Fri, 2006-07-28 at 14:23, Mingzuo Shen wrote:
> > Thanks Aaron.
> >
> > No. pg_dump, psql do not "see" those files.
> > As I said, psql -l shows "nothing".
> > pg_dumpall outputs nothing.
> >
> > strings 3476895975
> >
> > for example, does show a lot of text,
> > some of them seem to be actual data
> > that I am interested in extracting.
> >
> > If I create a new db and create new tables
> > in the new db, then they work as usual.
> >
> >
> >
> > --- Aaron Bono <postgresql@aranya.com> wrote:
> >
> > > On 7/22/06, Shen, Mingzuo <mshen@bcm.edu> wrote:
> > > >
> > > > Hello,
> > > >
> > > > I see some OS files (50+ GB total) but cannot
> see
> > > anything in psql -l.
> > > > There seem to be some big tables there.
> > > > I wonder if there are some tools that would
> dump
> > > the tables in text.
> > > > or, how to make PostgreSQL "connect" to these
> > > files again?
> > > >
> > >
> > > You can dump the whole database contents with
> > > pg_dump. This dumps your
> > > whole database with data into a text file. Is
> this
> > > what you mean?
> > >
> > >
> >
>
==================================================================
> > > Aaron Bono
> > > Aranya Software Technologies, Inc.
> > > http://www.aranya.com
> > >
> >
>
==================================================================
> > >
> >
> >
> > ---------------------------(end of
> broadcast)---------------------------
> > TIP 5: don't forget to increase your free space
> map settings
>
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: mzshen@yahoo.com, smarlowe@g2switchworks.com
Subject: Re: Read db files directly
In-Reply-To: <20060728194301.67345.qmail@web60416.mail.yahoo.com>
References: <1154115153.31664.129.camel@state.g2switchworks.com> <20060728194301.67345.qmail@web60416.mail.yahoo.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox