From: | Neil Conway <nconway(at)klamath(dot)dyndns(dot)org> |
---|---|
To: | dek(at)mit8(dot)ru |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: Bug #686: growing tables |
Date: | 2002-06-07 18:56:01 |
Message-ID: | 20020607145601.0e1bf553.nconway@klamath.dyndns.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Fri, 7 Jun 2002 12:20:11 -0400 (EDT)
"pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org> wrote:
> When I executing updates on small table (250 rows)
> it tables grows.
This is expected due to MVCC.
> In my database one table contains only 250 rows
> (two number, ip and date) take 170MB disk space!
>
> If I drop and create table (with export and import data) - all right
> but leter it begin growing
>
> command 'valuum' dont help.
No, but does VACUUM or VACUUM FULL help?
Can you isolate what is actually growing (e.g. indexes, tables, etc.)?
How many updates are you performing? How fast is the table growing?
Cheers,
Neil
--
Neil Conway <neilconway(at)rogers(dot)com>
PGP Key ID: DB3C29FC
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2002-06-07 21:41:09 | Re: [PATCHES] A bug in gist code with fetch/move |
Previous Message | pgsql-bugs | 2002-06-07 16:20:11 | Bug #686: growing tables |