Well, I take that back -- I guess I should have tried the "vacuum full analyze"
first, as that ALSO fixed the problem in the original (RHEL5 Postgres) database.
I guess I'll go back to the old database version.
I don't know why the NEW Postgres could import the data just fine and work
well whereas the old version had problems...
- Matt
> -----Original Message-----
> From: Matthew Goheen [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, October 23, 2007 11:48 AM
> To: 'Jesse Vincent'
> Cc: '[email protected]'
> Subject: RE: [rt-users] Strange custom field performance
> issue after upgrading to RT 3.6.4
>
> > Have you done a "FULL VACUUM ANALYZE" recently? It looks like the
> > statistics engine is...confused. That's the best way to reset it.
>
> I didn't think that would help as the data was just imported a week ago, and
> almost nothing has been done to the database since.
>
> However, this morning I tried upgrading to the latest Postgres (8.2.5) and
> that totally fixed the problem. I will try going back to the old database
> just to ensure that the "FULL VACUUM ANALYZE" will NOT fix it, but at this
> point I'm fairly certain there must have been some sort of database issue
> in the Postgres that ships with RHEL5.
>
> I'll send a follow-up with the final result of that test.
>
> - Matt
_______________________________________________
http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users
SAVE THOUSANDS OF DOLLARS ON RT SUPPORT:
If you sign up for a new RT support contract before December 31, we'll take
up to 20 percent off the price. This sale won't last long, so get in touch
today.
Email us at [EMAIL PROTECTED] or call us at +1 617 812 0745.
Community help: http://wiki.bestpractical.com
Commercial support: [EMAIL PROTECTED]
Discover RT's hidden secrets with RT Essentials from O'Reilly Media.
Buy a copy at http://rtbook.bestpractical.com
