| From: | David Lizano <david(dot)lizano(at)izanet(dot)com> |
|---|---|
| To: | pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: Recommended VACUM timing... |
| Date: | 2001-04-04 06:53:18 |
| Message-ID: | 4.3.2.7.0.20010404085251.00c31180@192.168.1.1 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
>For large tables that require a 24/7 uptime and see around 6-10 million
>changes a day, how do I run VACUM without taking the database/table down.
>Considering moving from MySQL, but can't quite understand how to run
>PostgreSQL in a production enviroment properly.
a) Using replication, you can "vacuum" one server meanwhile the other is
working.
There are two utilities for PostgreSQL v7.1 (eRServer and RServ
v0.1), but I don't know the level of maturity of this utilities. I suppose
that they aren't in production level.
b) 1.- Stop the postmaster daemon
2.- Make a copy of the database files directly from the filesistem.
3.- start the postmaster daemon.
The second should stop the service a short time compared with
"vacuumdb".
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Matthew | 2001-04-04 16:43:59 | RE: Recommended VACUM timing... |
| Previous Message | Grant | 2001-04-03 23:38:25 | Backup postgresql server. |