There's a problem somewhere in postgresql-dump which is called by the post-installation script, but I can't find it. I would welcome help from anyone who can take a look and find where the bug is.
Problem: under some circumstances, /etc/postgresql/pg_hba.conf is overwritten by a one line file reading "local all trust". This must be done by postgresql-dump in order to assure itself full access so that it can do the dump and restore for a new database version of postgresql, but the trap statements in the script should restore the proper pg_hba.conf (unless someone does kill -9). For unkown reasons the proper file is not being restored during some upgrades. It looks as though postgresql-dump is being called when an upgrade is not needed, but I'm not sure if this is a result or a cause of the problem. -- Oliver Elphick [EMAIL PROTECTED] Isle of Wight, UK http://www.lfix.co.uk/oliver GPG: 1024D/3E1D0C1C: CA12 09E0 E8D5 8870 5839 932A 614D 4C34 3E1D 0C1C ======================================== "Be strong, and let your heart take courage, all you who hope in the Lord." Psalm 31:24
