At some point in development, you may want to make a copy of your existing development database to play with an unstable new feature. Postgres makes it super trivial to do that by allow us to create a new database by using existing database as a template.
In postgres console, run
=# CREATE DATABASE new_database_name WITH TEMPLATE original_database_name;
Boom!, you got a cloned database named new_database_name.
Credit: Creating a copy of a database in Postgres
I’ve seen a convenient way to make a clone across remote server too. (Haven’t try) How to copy postgres database to another server
Instead of running command in psql, we can use createdb with -T flag like so
$ createdb -T original_database_name new_database_name
This guide shows you a simple way to fix your mdadm raid based drives which are not syncing or in the auto-read-only mode.
To find the names of your drives which are under auto-read-only mode or not syncing
Force the drives to sync.
mdadm --readwrite /dev/md9
Replace md9 with the name of the drive like md127 etc.
server ~ # cat /proc/mdstat
Personalities : [raid0] [raid1] [raid6] [raid5] [raid4] [raid10] [linear] [multipath]
md125 : active (auto-read-only) raid1 sda1 sdb1
192640 blocks [2/2] [UU]
md126 : active raid1 sda5 sdb5
97650944 blocks [2/2] [UU]
md127 : active raid1 sdb2 sda2
97659008 blocks [2/2] [UU]
[=>...................] resync = 8.8% (8686848/97659008) finish=64.0min speed=23148K/sec
md128 : active (auto-read-only) raid1 sdb6 sda6
288875200 blocks [2/2] [UU]
Source Info: http://wiki.crowncloud.net/doku.php/how_to_fix_auto-read-only_mdadm