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 4A547CB20200002500028589@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>)
List pgsql-admin
Jennifer Spencer <jenniferm411@hotmail.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

pgsql-admin by date:

Previous
From: "Kevin Grittner"
Date:
Subject: Re: Catching up Production from Warm Standby after maintenance - Please help
Next
From: Chris Browne
Date:
Subject: Re: Catching up Production from Warm Standby after maintenance - Please help