Re: Vacuum (table performance)

From: "Claudio Lapidus" <clapidus(at)hotmail(dot)com>
To: tgl(at)sss(dot)pgh(dot)pa(dot)us
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Vacuum (table performance)
Date: 2003-06-25 23:16:42
Message-ID: BAY7-F4dqJL947FR7mO000008c6@hotmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-general


Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
>
>"Claudio Lapidus" <clapidus(at)hotmail(dot)com> writes:
> > ... we are seeing increasing execution times, not for the
> > function but for the vacuum itself.
>
>Does a REINDEX of the table fix it?
>

Hmm, I'm looking at the documentation and it says that REINDEX acquires an
exclusive lock on the table. Does this mean that during the reindex
operation the table is unavailable for read/write by other processes?

An alternative suggested right there is to drop and recreate an index, where
-it says- CREATE INDEX would get a write lock on the table. Does this mean
that during the create index operation the whole table is unavailable for
write by other processes?

thanks again
cl.

_________________________________________________________________
Protect your PC - get McAfee.com VirusScan Online
http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Alvaro Herrera 2003-06-25 23:22:36 Re: Vacuum (table performance)
Previous Message Tom Lane 2003-06-25 22:43:07 Re: Vacuum (table performance)