Thread: Bug #686: growing tables

Dmitry Kishchukov (dek@mit8.ru) reports a bug with a severity of 1
The lower the number the more severe it is.

Short Description
growing tables

Long Description
When I executing updates on small table (250 rows)
it tables grows. 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.

What is this?

Sample Code


No file was uploaded with this report

On Fri,  7 Jun 2002 12:20:11 -0400 (EDT)
"pgsql-bugs@postgresql.org" <pgsql-bugs@postgresql.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@rogers.com>
PGP Key ID: DB3C29FC