Received: from maia.hub.org (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id B78E363334D for ; Sat, 20 Feb 2010 22:06:47 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 87424-03 for ; Sun, 21 Feb 2010 02:06:36 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from gw.wicourts.gov (gwmta.wicourts.gov [165.219.244.99]) by mail.postgresql.org (Postfix) with ESMTP id 229116332E8 for ; Sat, 20 Feb 2010 22:06:37 -0400 (AST) Received: from Courts-MTA by gw.wicourts.gov with Novell_GroupWise; Sat, 20 Feb 2010 20:06:35 -0600 Message-Id: <4B8040C6020000250002F42D@gw.wicourts.gov> X-Mailer: Novell GroupWise Internet Agent 8.0.1 Date: Sat, 20 Feb 2010 20:06:30 -0600 From: "Kevin Grittner" To: Cc: Subject: Re: Backups Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.11 tagged_above=-10 required=5 tests=BAYES_05=-1.11 X-Spam-Level: X-Archive-Number: 201002/163 X-Sequence-Number: 33766 Nilesh Govindarajan wrote: > I can prevent the changes to the database when the > backup is going on, but how do I grant the permissions ? I don't > want to key in the password for the superuser in the script. There are so many ways to deal with that that it's hard to make a suggestion without knowing more. You could just use CREATE USER and GRANT to set things up, you could use trust authentication in the pg_hba.conf to grant a database superuser permission from a secure machine, or you could use a pgpass file. (Check the documentation for details.) If I got creative I could probably come up with more, but I'm shooting in the dark here. -Kevin