X-Git-Url: http://erislabs.net/gitweb/?a=blobdiff_plain;f=doc%2FMAINTENANCE.postgresql;h=434a87fd9abcfd485afc3063c6ed9aa9fac1e8c5;hb=5bcaba15dc3f1984aed082d85c268cfd0f98b826;hp=df5cae54b42d7825660f804f71a9086aa6c11b2d;hpb=14056d8a61e9e0d01d0de17cff2d9e548cc8e3ed;p=mir.git

diff --git a/doc/MAINTENANCE.postgresql b/doc/MAINTENANCE.postgresql
index df5cae54..434a87fd 100755
--- a/doc/MAINTENANCE.postgresql
+++ b/doc/MAINTENANCE.postgresql
@@ -1,39 +1,28 @@
-To dump mir database <dbname>:
-	pg_dumplo -a -d <dbname> -s /dumpdir/dir
-	pg_dump -c -D -f /dumpdir/<dbname>.sql <dbname>
-this generates a dir with all blobs and a sql-file with all data.
 
-To restore the database:
-	psql <dbname> < <dbname>.sql
-	pgdump_lo -i -d <dbname> -s /dumpdir/dir
+DUMP & RESTORE
 
-Every once in a while (or make a script) postgresql database should
-be "cleaned". See postgresql docs for commands VACUUM and VACUUM ANALYZE
+To dump the database use pg_dump
+
+  pg_dump -Ft -b -u -f dump.tar [name_of_database]
+
+To restore do the following
+
+  pg_restore -d [name_of_database] -U [dbuser] -Ft dump.tar 
+
+
+VACUUM and VACUUM ANALYZE
 
 Every once in a while (or make a script) postgresql database should
 be "cleaned". See postgresql docs for commands VACUUM and VACUUM ANALYZE
 
+MISC
+
 We also have misc. perl scripts to merge Large Objects from other DB's.
 these can be used as a basis to write your own custom scripts.
 
+
 USER MANAGMENT IN POSTGRESQL
 
--- set owner of datbase
-select * from pg_database;
-select * from pg_user;
-update pg_database set datdba=ID_FROM_PG_USER where datname=DATABASENAME
-
--- find all tables to grant privs / select is just building sql
--- to be exectued
-
-select 'grant all on '||relname||' to "de_indy";'
-from pg_class
-where relname not like 'pg%'
-order by relname;
-
--- alter table owner / select is just building sql
--- to be exectued
-select 'alter table '||relname||' owner to "de_indy";'
-from pg_class
-where relname not like 'pg%'
-order by relname;
\ No newline at end of file
+If you want to change the db user of a mir db, there's a script for 
+that in mir/dbscripts/extra.
+