X-Original-To: pgsql-admin-postgresql.org@postgresql.org Received: from localhost (wm.hub.org [200.46.204.128]) by postgresql.org (Postfix) with ESMTP id C1B399FB2D6 for ; Tue, 8 Aug 2006 23:54:24 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.128]) (amavisd-new, port 10024) with ESMTP id 07993-08 for ; Wed, 9 Aug 2006 02:54:24 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey- Received: from noel.decibel.org (noel.decibel.org [67.100.216.10]) by postgresql.org (Postfix) with ESMTP id BD41C9FB219 for ; Tue, 8 Aug 2006 23:54:23 -0300 (ADT) Received: from [192.168.42.113] (natpool.bovine.net [67.100.216.14]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by noel.decibel.org (Postfix) with ESMTP id 4073756437; Tue, 8 Aug 2006 21:54:22 -0500 (CDT) In-Reply-To: <20060806144710.68533.qmail@web38109.mail.mud.yahoo.com> References: <20060806144710.68533.qmail@web38109.mail.mud.yahoo.com> Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Cc: pgsql-admin@postgresql.org Content-Transfer-Encoding: 7bit From: Jim Nasby Subject: Re: pg_dump problem Date: Tue, 8 Aug 2006 11:47:32 -0500 To: Srinivas Iyyer X-Mailer: Apple Mail (2.752.2) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200608/103 X-Sequence-Number: 22646 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