From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Shuzo Kubo" <gardenweasel(at)hotmail(dot)com> |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: REINDEXing user table in non stand-alone? |
Date: | 2001-11-08 14:27:11 |
Message-ID: | 16722.1005229631@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
"Shuzo Kubo" <gardenweasel(at)hotmail(dot)com> writes:
> Does one need to go into stand-alone mode to
> reindex an user table?
No. The docs need some improvement in this area. The pushups mentioned
in the docs are really only necessary if you have a broken system index
that's sufficiently critical that the backend crashes before you can
execute REINDEX. (For instance, the indexes on pg_class are likely to
cause such problems.) The basic idea of the pushups is to start the
backend in a mode such that it doesn't use the indexes to access the
system catalogs.
> Is it safe to REINDEX an user table while in
> non stand-alone mode when other users are
> accessing it?
Not sure about that --- I believe it's safe in 7.2, but IIRC, REINDEX
didn't bother to acquire a LOCK on the table in earlier releases.
Best to shut down any other clients that might be trying to access the
damaged table. Or forget REINDEX and recover via DROP/CREATE INDEX.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Yeffer Ochoa Parra | 2001-11-09 04:28:27 | ODBC 16 bits for POSTGRESql (Please Help me) |
Previous Message | Shuzo Kubo | 2001-11-08 08:10:09 | REINDEXing user table in non stand-alone? |