Re: Forced quiesce

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(dot)LITTLE(at)orbitz(dot)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(dot)Little(at)orbitz(dot)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(dot)ru(at)gmail(dot)com / Skype: gray-hemp