X-Original-To: pgsql-php-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 93DEC53BA4 for ; Fri, 1 Apr 2005 05:59:00 +0100 (BST) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 56088-03 for ; Fri, 1 Apr 2005 04:58:55 +0000 (GMT) Received: from houston.familyhealth.com.au (houston.au.fhnetwork.com [203.22.197.21]) by svr1.postgresql.org (Postfix) with ESMTP id A87BC53C1E for ; Fri, 1 Apr 2005 05:58:54 +0100 (BST) Received: from houston.familyhealth.com.au (localhost [127.0.0.1]) by houston.familyhealth.com.au (Postfix) with ESMTP id E6DBE24FE0; Fri, 1 Apr 2005 12:58:53 +0800 (WST) Received: from [192.168.0.40] (work-40.internal [192.168.0.40]) by houston.familyhealth.com.au (Postfix) with ESMTP id C975D24FCE; Fri, 1 Apr 2005 12:58:53 +0800 (WST) Message-ID: <424CD58F.3040108@familyhealth.com.au> Date: Fri, 01 Apr 2005 13:01:03 +0800 From: Christopher Kings-Lynne User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Vishal Kashyap @ [SaiHertz]" Cc: pgsql-php@postgresql.org Subject: Re: PostgreSQL Backup Script References: <77b69d2105033120543ca670a7@mail.gmail.com> In-Reply-To: <77b69d2105033120543ca670a7@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.077 tagged_above=0 required=5 tests=AWL, FORGED_RCVD_HELO X-Spam-Level: X-Archive-Number: 200504/2 X-Sequence-Number: 3086 > One obvious solution was to use .pgpass but it does not appeal me > because it is again a security threat. > any pointers or help may lead to unlocked secret. .pgpass is the only way to do it that is NOT a security threat. You can set PGUSER and PGPASSWORD environmental variables, but they are easily readable from other processes. I suggest allowing the 'postgres' user to connect with 'ident sameuser' in pg_hba.conf from the localhost only, then always just run pg_dump as 'postgres'. Chris