Dear RT Developers:
my RT is a stock FC5 3.4.5 with PostgresSQL as backend. Poking around
the schema, I’ve noticed two redundant indexes:
Indexes:
“users_pkey” PRIMARY KEY, btree (id)
“users1” UNIQUE, btree (name)
“users2” btree (name)
That seemed strange to me, so off to the mailing list archive I went,
only to discover that this had already been discussed one and a half
years ago:
http://lists.bestpractical.com/pipermail/rt-devel/2004-September/006274.html
Why did not it make it into 3.2.2 (or why isn’t it in 3.4.5)?
Sincerely,
Dear RT Developers:
my RT is a stock FC5 3.4.5 with PostgresSQL as backend. Poking around
the schema, I’ve noticed two redundant indexes:
Indexes:
“users_pkey” PRIMARY KEY, btree (id)
“users1” UNIQUE, btree (name)
“users2” btree (name)
That seemed strange to me, so off to the mailing list archive I went,
only to discover that this had already been discussed one and a half
years ago:
Updated Pg indexes (was Re: [Rt-devel] using standalone httpd to debug RT slowness)
Why did not it make it into 3.2.2 (or why isn’t it in 3.4.5)?
I have no idea. The easiest thing is likely to fix it in the 3.6.0
database upgrade scripts.
That seemed strange to me, so off to the mailing list archive I went,
only to discover that this had already been discussed one and a half
years ago:
The Rt-devel September 2004 Archive by thread
006274.html
Why did not it make it into 3.2.2 (or why isn’t it in 3.4.5)?
heh… forgot all about that… I still use my modified indexes and
with RT 3.4.5 we find RT to be just incredibly fast and responsive,
even on large tickets (many transactions) with large attachments.
I’m sure it will screw me over when I try to upgrade 
at least I
have the antidote script to put things as they were.