--- Josh Berkus <josh@agliodbs.com> wrote:
> Bill,
>
> > What about if an out-of-the-ordinary number of
> rows
> > were deleted (say 75% of rows in the table, as
> opposed
> > to normal 5%) followed by a 'VACUUM ANALYZE'?
> �Could
> > things get out of whack because of that situation?
>
> Yes. You'd want to run REINDEX after and event like
> that. As you should now.
>
> --
> Josh Berkus
> Aglio Database Solutions
> San Francisco
>
Thank you. Though I must say, that is very
discouraging. REINDEX is a costly operation, timewise
and due to the fact that it locks out other processes
from proceeding. Updates are constantly coming in and
queries are occurring continuously. A REINDEX could
potentially bring the whole thing to a halt.
Honestly, this seems like an inordinate amount of
babysitting for a production application. I'm not
sure if the client will be willing to accept it.
Admittedly my knowledge of the inner workings of an
RDBMS is limited, but could somebody explain to me why
this would be so? If you delete a bunch of rows why
doesn't the index get updated at the same time? Is
this a common issue among all RDBMSs or is it
something that is PostgreSQL specific? Is there any
way around it?
thanks,
Bill
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
