From: | Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl> |
---|---|
To: | Claudio Lapidus <clapidus(at)hotmail(dot)com> |
Cc: | tgl(at)sss(dot)pgh(dot)pa(dot)us, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Vacuum (table performance) |
Date: | 2003-06-25 23:22:36 |
Message-ID: | 20030625232236.GC23586@dcc.uchile.cl |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Wed, Jun 25, 2003 at 08:16:42PM -0300, Claudio Lapidus wrote:
>
> 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?
Yeah.
> 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?
An alternative approach would be to create a second index indentical to
the one in place and drop the first one.
--
Alvaro Herrera (<alvherre[a]dcc.uchile.cl>)
"Las cosas son buenas o malas segun las hace nuestra opinion" (Lisias)
From | Date | Subject | |
---|---|---|---|
Next Message | MT | 2003-06-25 23:24:06 | selecting the record before the last one |
Previous Message | Claudio Lapidus | 2003-06-25 23:16:42 | Re: Vacuum (table performance) |