Received: from localhost (maia-5.hub.org [200.46.204.182]) by postgresql.org (Postfix) with ESMTP id 805A19FA377 for ; Sat, 3 Feb 2007 23:45:39 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.182]) (amavisd-new, port 10024) with ESMTP id 86969-09 for ; Sat, 3 Feb 2007 23:45:32 -0400 (AST) Received: from news.hub.org (news.hub.org [200.46.204.72]) by postgresql.org (Postfix) with ESMTP id 096A69FA344 for ; Sat, 3 Feb 2007 23:45:39 -0400 (AST) Received: from news.hub.org (news.hub.org [200.46.204.72]) by news.hub.org (8.13.8/8.13.8) with ESMTP id l143jcU6050959 for ; Sat, 3 Feb 2007 23:45:38 -0400 (AST) (envelope-from news@news.hub.org) Received: (from news@localhost) by news.hub.org (8.13.8/8.13.8/Submit) id l143G3g6046758 for pgsql-admin@postgresql.org; Sat, 3 Feb 2007 23:16:03 -0400 (AST) (envelope-from news) From: Christopher Browne X-Newsgroups: pgsql.admin Subject: Re: Backup Strategies? Date: Sat, 03 Feb 2007 22:07:43 -0500 Organization: cbbrowne Computing Inc Lines: 30 Message-ID: <87r6t6vcw0.fsf@wolfe.cbbrowne.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Complaints-To: usenet@news.hub.org X-message-flag: Outlook is rather hackable, isn't it? X-Home-Page: http://www.cbbrowne.com/info/ X-Affero: http://svcs.affero.net/rm.php?r=cbbrowne User-Agent: Gnus/5.1007 (Gnus v5.10.7) XEmacs/21.4.19 (linux) Cancel-Lock: sha1:HChny8q52PEmMahQfYfHxwvp+Pk= To: pgsql-admin@postgresql.org X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200702/48 X-Sequence-Number: 24513 After takin a swig o' Arrakan spice grog, josh@globalherald.net (Joshua Kramer) belched out: > Hello All, > > What strategies are people using for automated, script-based backup of > databases? There are a few I can think of: > > 1. Create a "db_backup" unix user and a "db_backup" pgsql user. Grant > READ access to all objects on all databases for the "db_backup" pgsql > user. Create a .pgpass file in the home directory of the "db_backup" > unix user. Backup as needed with a script run as the "db_backup" unix > user. > > 2. Create a "db_backup" unix user and repeat above, except using the > "postgres" db user. My department took the approach of having a set of "admin-specific" users, much in the spirit of 1. For backups, vacuuming, and replication, the respective clever names were dumpy, molly, and slony. (When auditors asked about the new users, there was much snickering...) We didn't create a special Unix account for it; that seemed unnecessary. -- (format nil "~S@~S" "cbbrowne" "linuxfinances.info") http://cbbrowne.com/info/rdbms.html Who wants to remember that escape-x-alt-control-left shift-b puts you into super-edit-debug-compile mode? (Discussion in comp.os.linux.misc on the intuitiveness of commands, especially Emacs.)