From: | <lnd(at)hnit(dot)is> |
---|---|
To: | <pgsql-general(at)postgresql(dot)org> |
Subject: | Postgres: VACUUM |
Date: | 2004-01-14 20:50:16 |
Message-ID: | 0A5B2E3C3A64CA4AB14F76DBCA76DDA44E2C9E@seifur.hnit.is |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Any comments on multi-versioning problem:
As far as I understand from PG documentation, *CURRENTLY* VACUUM must be run
regulary, otherwise:
-Q. database will grow as fast as there are many DML going on it, won't it?
-Q. transaction ID may wrap - no doubt here.
-Q. Good news that VACUUM nowdays can run in parallel with other db activity
(non locking mode) and that pg_vacuum automates execution of VACUUM - this is
so, ins't it?
- Q. Bad knews that VACUUM must eventually scan every row(in fact, every row
and index pages?) in the database(?):
- if this is true(?) then can anyone give an idea on how long it runs
for a paticular size of the database and how much it slowdowns a database?
Thank you in advance,
Laimutis Nedzinskas
Reykjavik, Iceland
From | Date | Subject | |
---|---|---|---|
Next Message | Martin Marques | 2004-01-14 20:54:44 | Re: Max registers in postgresql 7.4 |
Previous Message | Rick Gigger | 2004-01-14 20:48:58 | Re: Postgress and MYSQL |