Re: Catching up Production from Warm Standby after maintenance - Please help

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: <scott(dot)marlowe(at)gmail(dot)com>, "Jennifer Spencer" <jenniferm411(at)hotmail(dot)com>
Cc: <scott(dot)lists(at)enterprisedb(dot)com>,<pgsql-admin(at)postgresql(dot)org>
Subject: Re: Catching up Production from Warm Standby after maintenance - Please help
Date: 2009-07-08 16:02:10
Message-ID: 4A547CB20200002500028589@gw.wicourts.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Jennifer Spencer <jenniferm411(at)hotmail(dot)com> wrote:

> Hm - Kevin, when you issue CLUSTER on your table, when do you switch
> the users over and do you let them keep writing during the process?
> Or is the second copy table read-only to the users while the
> cluster-build is happening on the primary (making it unavailable)?
> Thanks - and thanks for the Sybase difference explanation.

We only use CLUSTER occassionally, to recover from bloat caused by
exceptional circumstances (like mass deletes or a long-running
transaction from some will-behaved programmer.). CLUSTER has to lock
the table for the duration, blocking other users. We schedule this
off-hours.

I'm glad the info was useful. Our move from Sybase was incredibly
smooth, due largely to help from these PostgreSQL lists; I figure I
owe it to the community to give back as I am able. :-)

-Kevin

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Chris Browne 2009-07-08 16:17:14 Re: Catching up Production from Warm Standby after maintenance - Please help
Previous Message Kevin Grittner 2009-07-08 15:52:39 Re: Catching up Production from Warm Standby after maintenance - Please help