Skip site navigation (1) Skip section navigation (2)

Re: Vacuuming on heavily changed databases

From: "Gregory Williamson" <Gregory(dot)Williamson(at)digitalglobe(dot)com>
To: <zubac(at)vlayko(dot)tv>, "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-20 00:57:58
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-general
Sorry for top-posting -- challenged reader, but less challenged than running 8.2.0 -- upgrade to latest release -- 8.2.7! There were many fixes after the initial release and you're risking some bad mojo.

Greg Williamson
Senior DBA

Confidentiality Notice: This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information and must be protected in accordance with those provisions. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message.

(My corporate masters made me say this.)

-----Original Message-----
From: pgsql-general-owner(at)postgresql(dot)org on behalf of Dragan Zubac
Sent: Mon 5/19/2008 4:44 PM
To: Bohdan Linda
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: [GENERAL] Vacuuming on heavily changed databases
> Hello
> I have some similar situation like Yours,we're using at the moment PG 
> 8.2.0. 

In response to

pgsql-general by date

Next:From: ChrisDate: 2008-05-20 01:15:49
Subject: Re: Create database without entering password at command line
Previous:From: Gurjeet SinghDate: 2008-05-20 00:48:22
Subject: Re: Join three fields into one on same table

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group