Skip navigation.
Home
Freeware and Free & Open Source Software for Proprietary OSes

Reply to comment

Ray: Thanks for your

Ray: Thanks for your detailed response. As I mentioned in the original post, I verified from the installation instructions that a dump/restore was necessary. The point is that this is an incredibly poor practice to adopt as a standard. It is incredibly time consuming to dump and then restore. Any database requires regular backups (a dump of some kind). But, MySQL, for example, does not require a full restore after a major backup (say going from version 4 to 5). It also doesn't make sense that PostgreSQL could not restore its own generic SQL dump or that it required each database to be reinitiated before it could be restored. The pgAdmin problem did indeed turn out to be a pg_hba.conf problem. This was probably because I rebuilt from source (instead of an RPM install) and it overwrote my previous 8.2 version. I assumed that the "make install" would work the way Apache httpd's does during a source code install and check for an existing conf file and use it instead of a new raw conf file.

Reply

The content of this field is kept private and will not be shown publicly.