| From: | Teodor Cimpoesu <teo(at)digiro(dot)net> |
|---|---|
| To: | |
| Cc: | PostgreSQL general mailinglist <pgsql-general(at)postgreSQL(dot)org> |
| Subject: | Re: [GENERAL] oid_index size problem |
| Date: | 1999-09-17 15:07:04 |
| Message-ID: | 37E25918.AC9C5469@digiro.net |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Sebestyen Zoltan wrote:
>
> Hi,
>
> I wrote an application that uses PgSQL as database backend. It ran for
> almost a year and now it's database directory grew to 85633Kbyte.
> Inspecting this directory, I found out that a file called oid_index grew
> to 84058112 bytes, i.e. 99% of the database is index. What went wrong?
> What can be done now? I use a PgSQL 6.4.2 on a AIX 4.2..
>
> THanks in advance
just a wild guess, have you ever run vacuum ?
--
CIMPOESU Teodor, Web Programmer
@ DIGICOM S.A. Bucharest, Romania
@ Internet, site development
@ teo(at)digiro(dot)net,+(401)-330.47.28
official home page ~ http://www.digiro.net/
Internet web page ~ http://internet.digiro.net/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Daniel Stolk | 1999-09-17 16:46:28 | How to install patch. |
| Previous Message | Sebestyen Zoltan | 1999-09-17 14:37:08 | vacuum error - 6.4.2 database.. |