From: Jim Nasby <jnasby@pervasive.com>
To: Srinivas Iyyer <srini_iyyer_bio@yahoo.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: pg_dump problem
Date: Tue, 8 Aug 2006 11:47:32 -0500
Message-ID: <DDFD3195-92C3-48A8-9ED0-EF8178B0F847@pervasive.com> (raw)
In-Reply-To: <20060806144710.68533.qmail@web38109.mail.mud.yahoo.com>
References: <20060806144710.68533.qmail@web38109.mail.mud.yahoo.com>
On Aug 6, 2006, at 9:47 AM, Srinivas Iyyer wrote:
> I have two databases in my system.
>
> In firstdb i am having the following problem:
> firstdb=# \d targets
> ERROR: could not access status of transaction 362
> DETAIL: could not open file
> "/var/lib/pgsql/data/pg_clog/0000": No such file or
> directory
>
> when I vacuumed it:
> $ vacuumdb firstdb
> vacuumdb: vacuuming of database "firstdb" failed:
> ERROR: could not access status of transaction 11
> DETAIL: could not open file
> "/var/lib/pgsql/data/pg_clog/0000": No such file or
> directory
You didn't mention what version you're using, but this sounds a lot
like a corruption problem.
> Second problem:
>
> Issue with secondb - arraydb
>
> $ vacuumdb arraydb
> VACUUM
>
> Suspecting there is something going on with
> postgres,
> I wanted to take a backup of the arraydb.
>
> here is what I am doing:
>
> $ sudo pg_dump arraydb >
> arraydb_bcup_Aug_05_2006.dump
>
> There is nothing in this. I created dumps long back
> and they are heavy.
> I restarted the postgre server /etc/init.d/postgres
> restart Despite this, I am having problems.
>
> $ ls -lh
> total 8.0K
> -rw-r--r-- 1 speri postgres 0 Aug 5 20:17
> arradb_bcup_Aug_05_2006.out
Just where did that out file come from?
> What is in the /var/lib/pgsql/data/pg_clog
> $ sudo ls -lh /var/lib/pgsql/data/pg_clog
> total 80K
> -rw------- 1 postgres postgres 72K Aug 5 20:12 0001
>
> Logs:
>
> Surprisingly my logs is empty . Is this because I
> restarted the server.
Probably not, unless it's something the init.d script (which we have
nothing to do with) is doing. You probably have logging mis-
configured, or you're looking in the wrong place.
--
Jim C. Nasby, Sr. Engineering Consultant jnasby@pervasive.com
Pervasive Software http://pervasive.com work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461
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: jnasby@pervasive.com, srini_iyyer_bio@yahoo.com
Subject: Re: pg_dump problem
In-Reply-To: <DDFD3195-92C3-48A8-9ED0-EF8178B0F847@pervasive.com>
References: <20060806144710.68533.qmail@web38109.mail.mud.yahoo.com> <DDFD3195-92C3-48A8-9ED0-EF8178B0F847@pervasive.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