Thread: reindexdb
Hello,
We have a small (2GB) 8.4.20 database. The prior maintainer ran a reindexdb
twice a day (originally started with 7.3.x). Can anybody see a reason why we need to
continue to do this?
Thanks,
We have a small (2GB) 8.4.20 database. The prior maintainer ran a reindexdb
twice a day (originally started with 7.3.x). Can anybody see a reason why we need to
continue to do this?
Thanks,
--
Stephen Clark
NetWolves Managed Services, LLC.
Director of Technology
Phone: 813-579-3200
Fax: 813-882-0209
Email: steve.clark@netwolves.com
http://www.netwolves.com
Stephen Clark
NetWolves Managed Services, LLC.
Director of Technology
Phone: 813-579-3200
Fax: 813-882-0209
Email: steve.clark@netwolves.com
http://www.netwolves.com
On 04/29/2014 07:22 AM, Steve Clark wrote:
Hello,
We have a small (2GB) 8.4.20 database. The prior maintainer ran a reindexdb
twice a day (originally started with 7.3.x). Can anybody see a reason why we need to
continue to do this?
I don't. It certainly appears to be a piece of duct-tape put on either due to a real or perceived ancient bug or due to somebody's misunderstanding of things in the distant past. (I would, however, start looking at upgrading from 8.4 which is EOL in about 3 months.)
Cheers,
Steve
On Tue, Apr 29, 2014 at 10:22 AM, Steve Clark <sclark@netwolves.com> wrote: > We have a small (2GB) 8.4.20 database. The prior maintainer ran a reindexdb > twice a day (originally started with 7.3.x). Can anybody see a reason why we > need to > continue to do this? I used to re-index regularly with earlier 6.x and 7.x releases too. Not quite twice a day, though. I see no reason for it in any current Pg release.