definitely-- restarted the server, rebooted, i don't recall if i tried switching from PHP5 to PHP4 though (now that i have that option)-- but nothing i could figure under "normal" conditions would make it work-- of course unless there's something i've left out, or done incorrectly as listed above.
should i have tried, or should i try a different version?
(however, i got the impression that this release is the really "kickass" release)
NOTE:
one reason for this sudden streak of experimentation w/ PG is because i recently had a power supply issue in my old Box. loaded a fresh XP on a 40gig lying around here and used that as a new master for this hand-me-down, "new Box", and slaved my old Box's HDD to that one-- so i had a clean OS, and a slaved drive w/ a bunch of stuff on it-- when i installed the PostgreSQL, it went onto the Fresh OS-- and, for what it's worth, on the "new Box" master HDD along w/ , also freshly installed on the new hdd, a working Apache2, PHP4 (which was commented out in favor of my "old HDD's" properly functioning PHP5, commented to the new Apache) and, at the time of this "error" above, a malfunctioning MySQL 5 (no, mysql went on after postgres, i think).
throughout the course of setting up this "new" box, i noticed that it was booting w/ my older HDDs from the "old" box, so due to time-sensitive client-Project issues, i ultimately ended up "mastering" the "old" box's HDD in the "new" box-- kinda crazy, but cool that it "works" because it's like i have my old system back-- only on a newer faster box!... point being, now the drive where Postgres install resides is a Slave to this one-- so, when / if i go back to this, i'll probably just try again, installing PostgreSQL fresh on this the frankenstien "newBox-oldMaster" drive.
(hope that made sense!)
if i do a fresh install on this drive, do you have any recommendations? any rules of thumb i should go by, or keep in mind?
thanks!!