Once I've found I can continue using Drupal with PostgreSQL, here comes my next problem.
Apparently, my database has been getting more and more damaged on the trip from Drupal 4.1 (with alpha psql support) to 4.5. Right now, the site works at first glance, but quite a few things don't:
- it seems all the sequences were reset, or are not working properly. Doing stuff like creating a new vocabulary won't work.
- node hit count stopped working after the 4.5 upgrade
- psql permissions in the database might be wrong, and could be the root of all of this b0rkage.
- in general, I haven't completed an upgrade successfully since 4.2, I think I always need to cleanup due to the database inconsistency.
So, what can I do to fixup the database?
First I'd need to identify what parts of it are not synced with the current clean template.
I'll also have to go over all the sequence tables and check that they are correct. Can anyone tell me how to tell if the sequences are synchronised?
Finally, how should the database permissions look like? Right now, it's a mess, some tables look like this:
public | accesslog | {postgres=a*r*w*d*R*x*t*/postgres,triatlo=arwdRxt/postgres}
Others, like this:
public | comments_seq | {triatlo=a*r*w*d*R*x*t*/triatlo}
Others, which definitely look wrong (my psql user is in there):