| From: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
|---|---|
| To: | Bohdan Linda <bohdan(dot)linda(at)seznam(dot)cz> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Vacuuming on heavily changed databases |
| Date: | 2008-05-19 15:19:07 |
| Message-ID: | 20080519151907.GC14142@svana.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Apart from reinterating what someone else: you're not vacuuming
anywhere near often often. Normal vacuum takes no locks.
On Mon, May 19, 2008 at 04:50:18PM +0200, Bohdan Linda wrote:
> 3) There were suggestions (in archives) doing dump and then restore on
> dropped database, but still requires downtime.
CLUSTER will rebuild the table with only the actually used records in
it. It also requires an exclusive lock so try to keep it small :)
Have a nice day,
--
Martijn van Oosterhout <kleptog(at)svana(dot)org> http://svana.org/kleptog/
> Please line up in a tree and maintain the heap invariant while
> boarding. Thank you for flying nlogn airlines.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bohdan Linda | 2008-05-19 15:24:11 | Re: Vacuuming on heavily changed databases |
| Previous Message | Harald Armin Massa | 2008-05-19 14:59:42 | Re: Vacuuming on heavily changed databases |