Re: Catching up Production from Warm Standby after maintenance - Please help - Mailing list pgsql-admin

From Kevin Grittner
Subject Re: Catching up Production from Warm Standby after maintenance - Please help
Date
Msg-id 4A53371A02000025000284BA@gw.wicourts.gov
Whole thread Raw
In response to Re: Catching up Production from Warm Standby after maintenance - Please help  (Jennifer Spencer <jenniferm411@hotmail.com>)
Responses Re: Catching up Production from Warm Standby after maintenance - Please help  (Jennifer Spencer <jenniferm411@hotmail.com>)
List pgsql-admin
Jennifer Spencer <jenniferm411@hotmail.com> wrote:

> I think that we won't be able to do vacuuming/reindexing with the
> machine online and serving users if the database is over a certain
> size.  Am I wrong?

Probably.  My first concern is to make sure you aren't doing VACUUM
FULL as part of your maintenance cycle.  That option is meant for
recovery from extreme bloat, and is sort of a "last resort".  Other
vacuums coexist with normal usage as long as you have things properly
configured for your environment.  You probably won't have a need to
reindex if you stay away from VACUUM FULL and otherwise avoid unusual
activity which causes index bloat; however, if you do need to reindex
without down time, there is CREATE INDEX CONCURRENTLY which can be
used to achieve that.

-Kevin

pgsql-admin by date:

Previous
From: Jennifer Spencer
Date:
Subject: Re: Catching up Production from Warm Standby after maintenance - Please help
Next
From: Jennifer Spencer
Date:
Subject: Re: Catching up Production from Warm Standby after maintenance - Please help