FullText Searching: The Dilemma

Greg Hendricks ghendricks at novell.com
Tue Jun 26 17:51:54 UTC 2007

On Tuesday 26 June 2007 11:18, Frédéric Buclin wrote:
> >> Or, of course, just recommend that large installs use
> >> postgres+tsearch? ;)
> >
> > We could do that. How hard would it be to convert b.m.o.? Are there
> > scripts, or do all conversions have to be done by hand? Do we know how
> > MoCo IT would feel about supporting Postgres? Do we feel the Postgres
> > support is stable enough? Are there other downsides?
> I second this idea. Instead of using some external program (which I'm
> against. We already depend on (too) many Perl modules), we could say
> that big installations move to PostgreSQL if they have perf problems.
> Bugzilla 2.22 and higher run on PostgreSQL as fine as it runs on MySQL.
> We do QA on both DB with exactly the same tests and no failure has been
> detected with PostgreSQL.
As wonderful as I am sure Postgres is, I don't see us moving to it any time 
soon. We have commercial support for MySQL and I don't think the bosses will 
be willing to renegotiate on a new DB provider (do they even have commercial 
support for PostGres?) in the next couple years. I don't think you can 
require that "Large installations" move to it. How do you define Large? Does 
that mean it is ok to start with MySQL when you are "Small" and then Bugzilla 
warns you when you reach your 100,000th bug that you now need to switch? I 
don't think that is viable.

More information about the developers mailing list