Frank Finner wrote:
Seems we have been hunting the wrong bugs in the beginning. Could it be possible that
there was a
major version update of the database engine (7.2.x -> 7.4.x for example), without a
database reload?
I have noticed several new "features" for queries, I think, 7.4 is much closer to SQL
standards than
7.3, which, in turn, is closer than 7.2, especially regarding the necessity of type
casts. In one of
our applications we had to rewrite most of the queries, because they did not work
properly with
newer PostgreSQL releases. So that could have caused the PHP-Errors, and the restart
of the database
without a dump/restore could then cause the start up failure. Just a theory.
3 weeks ago, i've upgraded my PostgreSQL server from 7.2.4 to 7.4.1.
In 7.2 i've dumped the tables with pg_dump and after the upgrade the
tables are reloaded with psql.
Did you compare the actual binaries and the binaries of the backup? Are they identical?
There are no Postgres binaries in /usr/local/pgsql, but in
/usr/local/bin.
Because i've only copied /usr/local/pgsql, the binaries are no changed.
--
E-mail : [EMAIL PROTECTED]
: [EMAIL PROTECTED]
Website : http://www.quicksteps.nl/
---------------------------(end of broadcast)---------------------------
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
