-----Original Message-----
From: pgsql-novice-owner@postgresql.org [mailto:pgsql-novice-owner@postgresql.org] On Behalf Of Carlo Ascani
Sent: Friday, September 02, 2011 1:42 AM
To: pgsql-novice@postgresql.org
Subject: Re: [NOVICE] Automated pg_Dump issue
On Wed, 31 Aug 2011 14:13:07 -0700
Chris Campbell <ccampbell@cascadeds.com> wrote:
>> The call string is:
>> "c:\program files (x86)\PostgreSQL\9.0\bin\PG_dump.exe" --create
>> --no-password --format="c" --superuser="postgres"
>> --username="postgres" --file="c:\temp\pg.backup" "dd3_000"
>>
>I'm not so strong in Windows, but specifying the -h 127.0.0.1
>option should be sufficient for you.
Thank you for your reply. Unfortunately it made no difference. I've revised the call somewhat based on some other
finetuning but the password prompt remains. And when I include the no-password parameter if fails with a no password
suppliederror
"c:\program files (x86)\PostgreSQL\9.0\bin\PG_dump.exe" --host="27.0.0.1" --username="postgres" --no-password
--file="c:\temp\pg.backup"--disable-dollar-quoting --format=plain --inserts --column-inserts "dd3_000"
What dark magic is involved in setting the pgpass.conf file to allow pg_dump to work without a password prompt? I set
itbased on the suggestion given in the older post but it doesn't seem to matter what I put in there:
(localhost:5432:dd3_000:postgres:postgres)
The pgpass.conf file exists in the root of my database cluster. Is that correct? Thanks for any suggestions...