RE: safety of vacuum verbose analyze on active tables

From: "Andrew Snow" <als(at)fl(dot)net(dot)au>
To: "Pgsql-General(at)Postgresql(dot) Org" <pgsql-general(at)postgresql(dot)org>
Subject: RE: safety of vacuum verbose analyze on active tables
Date: 2000-04-17 15:39:52
Message-ID: NHEALMDKDACEIPBNOOOCKEGCCCAA.als@fl.net.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general


> > > what is the relative safety of doing a vacuum verbose analyze
> on a 24Gb
> > > table while there are selects and updates/inserts happening on it?
> >
> > As far as I know, the table is locked completely during a Vacuum. Any
> > transactions attempting to do inserts/updates will be paused
> safely. So go
> > ahead and schedule your vacuums for whenever you need to.

> There have been reports of problems (corruption, etc.) when trying to do
> this. See the archive for a discussion along these lines a few
> months ago.

You've got to be joking.

Is the table locking mechanism in Postgresql broken??

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2000-04-17 15:41:19 Re: [HACKERS] safety of vacuum verbose analyze on active tables
Previous Message Ed Loehr 2000-04-17 15:31:50 Re: safety of vacuum verbose analyze on active tables