I could be wrong, but you also need the -a (analyze) option to vacuum to
have it "re-think" it's lookup strategies, right?
In article <am(dot)pgsql(dot)general(dot)965411449(dot)47605(at)illiad(dot)adhesivemedia(dot)com>,
Jeffrey A. Rhines <jrhines(at)email(dot)com> wrote:
>If you're worried about performance, a vacuum should do the trick,
>right?
>
>Jeff
>
>Patrick Robin wrote:
>>
>> Hi all,
>>
>> With Postgres 6.5.2, if a table has undergone several row deletions,
>> does it make sense/ is it needed to rebuild the index? Would this be
>> accomplished by
>> dropping it and then recreating it?