- Published:
- February 20, 2008 – 11:51 am
- Author:
- By Dave
When doing a PostgreSQL database server upgrade, you first need to backup all of the databases because the format changes from version to version. Postgresql documentation states you need to run the command: 1pg_dumpall > outputfile I ran this, and received the error message: 1pg_dumpall: could not connect to database "template1": FATAL: role "root" does not exist So after some head scratching and googling without any results; I noticed that I had created a user for postgres; namely ‘postgres’. I sued to that user and ran the command – what do you know – it works fine! I’m glad that error message was so clear. So, the thing that the documentation does not state – make sure you are running under the Postgresql user before running the backup command.
Categories: Linux,MySQL,System Administration
Tagged: backup, postgresql
- Published:
- August 14, 2007 – 10:40 am
- Author:
- By Dave
…and other MySQL Oddities. If your MySQL binary log files are a “Growing” problem… there are a few simple steps you can use to curtail their growth and save your disk space from these huge files. They probably look like: mysql-bin.000001 mysql-bin.000002 mysql-bin.000003 mysql-bin.000004 mysql-bin.000005 … And around 1 gig in size each. These files are generated when you have log-bin=mysql-bin or other log-bin= line in your /etc/my.cnf configuration file. There are two ways to fix this problem: The first is to stop the MySQL server from creating these binary files. The only reason you would need the binary log files is if you are doing mysql replication from a master to a slave. In this case, these files are necessary, at least until the slave(s) has caught up with the master. To stop this from logging, comment out (using #) the line containing ‘log-bin’. The second is to continue….
Categories: Configurations,MySQL,System Administration
Tagged: database server
