Vacuum returns error 
Author Message
 Vacuum returns error


Quote:

> > PG 7.2 and RH 7.2
> > Developer dropped ~30+ tables from 4 different DBs on the same
> > server.  Queiries began to fail: unable to locate file;
> > /var/lib/pgsql/pg_clog/0006.

> Hmm.  What files do you actually have in /var/lib/pgsql/pg_clog?
> (I'd like to see an ls -l of that directory if possible; the sizes
> and mod dates might be useful clues.)

total 252
-rw-------  1  postgres postgres  253952  apr  3  13:47  0000

  Another useful bit of info

Quote:
> would be "select * from pg_database".

database  datdba  encoding  datistemplate  datallowconn  datlassysoid  datvacuumxi
qc             100            0          false                true                16554            964425
plant1       100            0          false                true                16554            964106
template1  1               0          true                 true                16554            1810
template0  1               0          true                 false               16554            49
plant2        100           0          false                true                16554            964326
plant3        100           0          false                true                16554            964264

Best of luck

- William

---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate

message can get through to the mailing list cleanly



Mon, 20 Sep 2004 04:40:55 GMT
 Vacuum returns error

Quote:

> Developer dropped ~30+ tables from 4 different DBs on the same
> server.  Queiries began to fail: unable to locate file;
> /var/lib/pgsql/pg_clog/0006.

>> Hmm.  What files do you actually have in /var/lib/pgsql/pg_clog?
> [ info snipped ]

Okay.  It seems quite clear that you've executed less than a million
transactions so far in this installation; so 0000 is the only clog
segment that does or should exist, and there's no valid reason
for anything to be trying to access segment 0006.  I do not think
this could be a clog logic error as I first suspected; it's probably
more like a garden-variety data corruption problem, ie, something
dropped a bit and there's now an xmin or xmax field someplace that
contains a bogus transaction ID up in the six-million-something range.

My advice is to try to track down and get rid of the bad tuple.

                        regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?

http://www.postgresql.org/users-lounge/docs/faq.html



Mon, 20 Sep 2004 04:51:33 GMT
 
 [ 2 post ] 

 Relevant Pages 

1. Vacuum return codes (vacuum as db integrity check?)

2. VACUUM on database with open transaction returns error?

3. Vacuum and Vacuum analyse

4. Still confused about VACUUM vs. VACUUM FULL

5. Vacuum VS Vacuum Analyze

6. VACUUM vs VACUUM ANALYZE

7. Question regarding effects of Vacuum, Vacuum Analyze, and Reindex

8. Vacuuming and re-indexing (was Re: Vacuum meaning)

9. VACUUM AND VACUUM ANALYSE

10. Query error corrected after vacuum

11. Help - Error in VACUUM

12. Error on Vacuum Full


 
Powered by phpBB® Forum Software