From: | Dave Cramer <pg(at)fastcrypt(dot)com> |
---|---|
To: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org> |
Subject: | Re: small pg_dump RFE: new --no-prompt (password) option |
Date: | 2006-12-01 13:59:04 |
Message-ID: | 04980DC3-41C6-44C5-8642-408E7ED98894@fastcrypt.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 1-Dec-06, at 8:13 AM, Martijn van Oosterhout wrote:
> On Fri, Dec 01, 2006 at 07:46:59AM -0500, Dave Cramer wrote:
>>>
>> I'm forwarding this on behalf of Marc Hebert
>
> I saw it the first time.
Sorry about the double posting
>
>>> When we implemented this scripting in Java we faced one major issue:
>>> pg_dump may prompt for a password in a unpredictable way
>>> (depending on
>>> the user misconfiguration). Taking care of this is surprisingly
>>> complex. The suggested --no-prompt would make scripting pg_dump
>>> infinitely easier. In case a password is needed, this option would
>>> simply fail and return immediatly with an appropriate error message.
>>> Or even better, with a well-defined return status.
>
> Seems to me that you could just do this by setting stdin to be
> /dev/null?
I think a well defined error message makes sense.
>
> Have a nice day,
> --
> Martijn van Oosterhout <kleptog(at)svana(dot)org> http://svana.org/
> kleptog/
>> From each according to his ability. To each according to his
>> ability to litigate.
From | Date | Subject | |
---|---|---|---|
Next Message | Csaba Nagy | 2006-12-01 14:07:01 | Re: small pg_dump RFE: new --no-prompt (password) option |
Previous Message | Martijn van Oosterhout | 2006-12-01 13:13:53 | Re: small pg_dump RFE: new --no-prompt (password) option |