From: | Stephane Tessier <stephane(at)info-logika(dot)com> |
---|---|
To: | "'scott(dot)marlowe'" <scott(dot)marlowe(at)ihs(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: table growing |
Date: | 2002-11-08 01:03:07 |
Message-ID: | 000d01c286c2$998e4350$6401a8c0@bug |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
The database version is Postgresql 7.2.1
And I run 4 time/day vacuum but I cannot lock tables so I don't want to
use a vacuum full.... the question is:is it a problem with pgsql or
Is it normal to have to stop the database to do maintenance...
My boss WANT (!!!!!) that we find the trouble but is there a trouble????
If it's normal... we'll have to live with it or migrate to Oracle...
Thanks a lot!
-----Original Message-----
From: scott.marlowe [mailto:scott(dot)marlowe(at)ihs(dot)com]
Sent: 7 novembre, 2002 12:18
To: Stephane Tessier
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: [GENERAL] table growing
On Mon, 4 Nov 2002, Stephane Tessier wrote:
> Hi
>
> I have a growing database problem. I insert rows in a table
> automatically(1500 by hour approx) and I use this table like a
temporary
> table 24/7.All rows inserted are
> deleted(maybe 12-24 hours later)but the database grow all the time I
> tried vacuum,analyze,vacuum full, reindex, max_fsm_pages
=100000,1000000
> etc.
>
> the only way to reduce space is dump table /drop table/create table
and
> insert after but after 12-24 hours. the table is very big and request
> are very slow
>
> 12G before the drop and 250m after the drop/create/insert.
Have you been running vacuum and vacuum full?
What version of Postgresql are you running, and what OS are you on?
From | Date | Subject | |
---|---|---|---|
Next Message | Lamar Owen | 2002-11-08 01:24:04 | Re: Hardware estimation |
Previous Message | W. A. Sanchez | 2002-11-08 00:40:23 | rebuilding pg_xlog from base files |