--howdy:
--this is what i was talking about when doing
--things like 'vacuum' and 'pg_dump'.
**vacuum error**
[snip]
test_db=> vacuum verbose analyze ref_dcg ;
NOTICE: --Relation ref_dcg--
NOTICE: Index ref_dcg_pkey: Pages 290047; Tuples 43600255: Deleted 1397955.
CPU 45.71s/74.86u sec elapsed 7755.21 sec.
FATAL 1: This connection has been terminated by the administrator.
server closed the connection unexpectedly
This probably means the server terminated abnormally
before or while processing the request.
The connection to the server was lost. Attempting reset: Succeeded.
test_db=>
[/snip]
**pg_dump error**
[snip]
Backing up schema for debborah_dev_bh_claimsum_4q02 ...
pg_dump: query to obtain list of indexes failed: ERROR: syscache lookup for index 4185182890 failed
[/snip]
--i'm looking for ways to move the data, save and
--repopulate the (new) database without losing
--much, if anything. if i could get some clean
--dumps, that would be cool ...
--i even have to export to MS Access for some
--smaller tables just to clean up some of the
--mess.
--anyway ... thanks.
-X
-----Original Message-----
From: Tom Lane [mailto:tgl@sss.pgh.pa.us]
Sent: Friday, June 20, 2003 11:05 AM
To: Johnson, Shaunn
Cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] splitting a table?
"Johnson, Shaunn" <SJohnson6@bcbsm.com> writes:
> --haven't done a vaccumdb / analyze
> --on the entire db lately because of
> --the errors i get
> FATAL 2: open of /var/lib/pgsql/data/pg_clog/0003 failed: No such file or
> directory
You need to be dealing with that, not ignoring it. An update to 7.2.4
might help.
regards, tom lane
