Re: Catching up Production from Warm Standbyaftermaintenance - Please help

From: Scott Mead <scott(dot)lists(at)enterprisedb(dot)com>
To: Lewis Kapell <lkapell(at)setonhome(dot)org>
Cc: Scott Whitney <swhitney(at)journyx(dot)com>, pgsql-admin(at)postgresql(dot)org
Subject: Re: Catching up Production from Warm Standbyaftermaintenance - Please help
Date: 2009-07-07 17:51:56
Message-ID: d3ab2ec80907071051y7fc880dbp1073396a3cc636bf@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

On Tue, Jul 7, 2009 at 1:46 PM, Lewis Kapell <lkapell(at)setonhome(dot)org> wrote:

>
>>
> If you were planning to upgrade to 8.4 in the near future, then you
> wouldn't have to worry about these settings any more. Those settings tune
> themselves and they are no longer specified in the configuration file.

+1

The visibility map also helps with vacuum, it keeps the amount of
un-necessary I/O down (if a whole block has 'live' rows anyway).

--Scott

>
>
> Lewis Kapell
>
>
>
> --
> Sent via pgsql-admin mailing list (pgsql-admin(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-admin
>

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Kevin Grittner 2009-07-07 17:54:47 Re: Catching up Production from Warm Standby aftermaintenance - Please help
Previous Message Scott Mead 2009-07-07 17:50:40 Re: Catching up Production from Warm Standby aftermaintenance - Please help