Hi all, before I get a stream of posts telling me my post would be more appropriate somewhere else, I consider this a drupal problem/challenge and am only asking for solutions that might solve the problem from a drupal perspective. I know I can use a postgres forum, but it is not a postgress issue, rather a drupal community one.
When d6 was in beta, we had already begun to design some applications based on postgresql, it was thought we could leverage some of those applications becuase postgres code had been part of drupal for quite some time, so we deployed 2 important sites in d6 based on pg.
Now we are finding that there are many issues with running pg, everything from module coders who dont have time to debug thier modules in pg and worse, who have never run pg or dont have pg to test their apps on. although in some cases I love being a beta tester and helping others out, in these circumstances, I really needed reliablilty, not new cutting edge, and I when we deployed d6 on pg I thought we might be getting that. It was my own mistake.
Now d7 in on the horizon, and pg still seems like a bad choice for us and we are considering was to migrate drupal 6 from pg back to something that is more mature in the code. I have heard of all kinds of solutions and fixes and workarounds, but what I want to know is:
Is there a seamless way to migrate a drupal install from postgres onto some other database . we have hundreds of nodes and can really afford no down time. If threre is no real effective way to do this, I will simply continue on PG and do my best to help module coders get thier code working correcty, but If Ican get these site onto a more mainstream (in the drupal world anyhow) db like mysql, I would.
Thanks in advance to any and all advice
Franco Nogarin
