On Wed, May 16, 2007 at 09:51:20AM -0700, Joshua D. Drake wrote:
> Jim C. Nasby wrote:
> >On Wed, May 16, 2007 at 09:42:36AM -0700, Joshua D. Drake wrote:
> >>>>
> >>>>I don't know that they would be happy unless they had someone with Pg
> >>>>experience helping them.
> >>>Is it the drupal code itself that's the issue or just a matter of tuning
> >>>PostgreSQL?
> >>Both. Obviously tuning postgresql is a big part but they have some odd
> >>query issues to deal with. And if they have *any* custom modules, oh boy.
> >
> >Well, while they're in pain it sounds like a good time to get them
> >thinking about changing preferred databases as well as cleaning up some
> >of the code... I'm sure that if their preferred database was PostgreSQL
> >you'd be seeing more work. :)
>
> Drupal 6 is dropping support for MySQl 3.x and going to a more
> normalized data structure. Partly because of me, partly because of a lot
> of others. I have spoken with Dries about it personally (via email) and
> he is very happy with the idea of moving to a more sane structure overall.
>
> However, there would be a *ton* of work to be done to get them to prefer
> PostgreSQL.
Seems like if switching made all their performance issues go away it
wouldn't be that hard...
Do they have any kind of benchmark they could use to test with?
--
Jim Nasby decibel@decibel.org
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)