| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Brickley Jeff-RA9607 <Jeff(dot)Brickley(at)motorola(dot)com> |
| Cc: | "'pgsql-admin(at)postgresql(dot)org'" <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: Vaccuum/Analyze |
| Date: | 2002-09-12 19:03:03 |
| Message-ID: | 8968.1031857383@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Brickley Jeff-RA9607 <Jeff(dot)Brickley(at)motorola(dot)com> writes:
> I am running PostgreSQL 7.2.1 on a Sun 5.8 OS. I have a database named metrics with 4 tables. A few of the tables contain approx. 10 million records. When I run a vaccuum/analyze with the following command:
> vacuumdb -d metrics -z -v
> the process 'hangs' for several hours and then an error message appears that says:
> vacuumdb: vacuum metrics failed.
> ERROR: RelationClearRelation: Relation 16599 deleted while still in use.
> Watching the stdout I see the process is 'hanging' on analyzing one of my tables called file_dup. This table has no data in it. What strikes me as odd is that I ran vacuumdb against the file_dup table itself:
> (vacuumdb -z -v -t 'file_dup' metrics) and it completed within seconds without errors.
I'd be inclined to wonder what else is accessing that database. Could
some other process be sitting with an open transaction that has that
table locked?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mel Jamero | 2002-09-12 20:44:33 | Re: Vaccuum/Analyze |
| Previous Message | info | 2002-09-12 17:45:45 | -i option |