From: | Michael Richards <miker(at)scifair(dot)acadiau(dot)ca> |
---|---|
To: | Michael Green <michael(dot)green(at)gbst(dot)com> |
Cc: | "'pgsql-sql(at)postgresql(dot)org'" <pgsql-sql(at)postgreSQL(dot)org> |
Subject: | Re: [SQL] Postgres Table grows very quickly? |
Date: | 1999-09-14 01:38:16 |
Message-ID: | Pine.BSF.4.10.9909132232590.63880-100000@scifair.acadiau.ca |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
On Tue, 14 Sep 1999, Michael Green wrote:
> UPDATE routerinfo SET lastdate = '09-14-1999', lasttime = '09:00' WHERE
> linkid = 'Sydney';
>
> Routerinfo is 8k after the initial update, from then on it grows 8k for
> every update. I never do an insert and it never grows beyond 16 rows. It
Check out mvcc. Basically running an update does duplicate the tuple. A
vacuum will reclaim the extra space. 8k (an entire page) seems a little
excessive for each updated tuple, but I don't really know anything about
how data is physically stored.
I generally run vacuum; once a night and vacuum analyze; once a week, but
that's more or less dependant on tyour database.
-Michael
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Richards | 1999-09-14 01:56:28 | Array Madness |
Previous Message | Michael Green | 1999-09-13 23:35:41 | Postgres Table grows very quickly? |