Re: Forced quiesce - Mailing list pgsql-admin

From Sergey Konoplev
Subject Re: Forced quiesce
Date
Msg-id AANLkTikFnQTMvptoZbsPXOiM_hubxxWvFEix-HXc9nX=@mail.gmail.com
Whole thread Raw
In response to Forced quiesce  ("Little, Douglas" <DOUGLAS.LITTLE@orbitz.com>)
List pgsql-admin
Hi,

David Fetter has an article about the issue like your. He describes the situation with DROP DATABASE but it could easily be adapted for VACUUM. Here is the link http://people.planetpostgresql.org/dfetter/index.php?/archives/63-Kick-em-out,-and-keep-em-out!.html

On 28 October 2010 16:39, Little, Douglas <DOUGLAS.LITTLE@orbitz.com> wrote:
>
> Hi,
>
> We’re having to vacuum full the system tables everyday due to the number of  temp table drop/creates.
>
> We’re finding that if anyone tries to execute a job during the maintenance period, it often hangs the db.
>
>  
>
> Is there a way that we can force the db to quiesce?  Or  lock out users.
>
> Luckly,  most users are coming in thru a network VIP, so all client IP’s are the same.
>
>  
>
> Thanks in advance.
>
>  
>
> Doug Little
>
>  
>
> Sr. Data Warehouse Architect | Enterprise Data Management | Orbitz Worldwide
>
> 500 W. Madison, Suite 1000  Chicago IL 60661| Office 312.260.2588 | Fax 312.894.5164 | Cell 847-997-5741
>
> Douglas.Little@orbitz.com
>
>    orbitz.com | ebookers.com | hotelclub.com | cheaptickets.com | ratestogo.com | asiahotels.com
>
>  


--
Sergey Konoplev

Blog: http://gray-hemp.blogspot.com /
Linkedin: http://ru.linkedin.com/in/grayhemp /
JID/GTalk: gray.ru@gmail.com / Skype: gray-hemp

pgsql-admin by date:

Previous
From: "Plugge, Joe R."
Date:
Subject: Re: Forced quiesce
Next
From: "Little, Douglas"
Date:
Subject: advantages of multiple db's