| From: | "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> |
|---|---|
| To: | <scott(dot)lists(at)enterprisedb(dot)com>, "Jennifer Spencer" <jenniferm411(at)hotmail(dot)com> |
| Cc: | <scott(dot)marlowe(at)gmail(dot)com>,<pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: Catching up Production from Warm Standby after maintenance - Please help |
| Date: | 2009-07-07 16:52:58 |
| Message-ID: | 4A53371A02000025000284BA@gw.wicourts.gov |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Jennifer Spencer <jenniferm411(at)hotmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jennifer Spencer | 2009-07-07 17:01:48 | Re: Catching up Production from Warm Standby after maintenance - Please help |
| Previous Message | Jennifer Spencer | 2009-07-07 16:42:01 | Re: Catching up Production from Warm Standby after maintenance - Please help |