small pg_dump RFE: new --no-prompt (password) option

From: Dave Cramer <pg(at)fastcrypt(dot)com>
To: PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org>
Subject: small pg_dump RFE: new --no-prompt (password) option
Date: 2006-12-01 12:46:59
Message-ID: 2A046899-4A18-4563-9C0A-13D691D083D2@fastcrypt.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

>
I'm forwarding this on behalf of Marc Hebert
>
> Hi there,
>
> As discussed recently on the jdbc mailing-list in this "Backup in
> Java" thread
>
> <http://thread.gmane.org/gmane.comp.db.postgresql.jdbc/12441/
> focus=12441>
>
> there is a significant interest in doing backups in an
> non-interactive, programmatic way. Reminder: AFAIK pg_dump is
> currently the very unique reliable way to perform a backup. There
> is no
> documented API or protocol to do this. Any program in any language is
> stuck with "scripting" pg_dump.
>
> 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.
>
> Thanks in advance for considering this new feature!
>
> Sincerely,
>
> Marc.
>
>

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message arkadiusz.staron 2006-12-01 13:07:15 Re: Tsearch + polish ispell + polish locale
Previous Message Heikki Linnakangas 2006-12-01 12:02:12 Re: FOR SHARE vs FOR UPDATE locks