From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Nigel Kukard" <nkukard(at)lbsd(dot)net> |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #1769: pg_dumpall fails to run |
Date: | 2005-07-14 18:35:40 |
Message-ID: | 21521.1121366140@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
"Nigel Kukard" <nkukard(at)lbsd(dot)net> writes:
> When pg_dumpall prompts me for the password I type it in, and press enter
> only to get another password prompt.
This doesn't seem particularly surprising: you are going to have to
enter the password once for pg_dumpall, and once for each of its
per-database invocations of pg_dump.
Most people try to set things up so that pg_dump(all) can be executed
without any manual password entry. You might be able to use another
authorization method for local connections; failing that, set up a
~/.pgpass file for the database superuser.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2005-07-14 20:57:07 | Re: BUG #1768: to_char result of an interval differs between 7.x and 8.x |
Previous Message | marco_0160 | 2005-07-14 15:48:36 | [postgres] Betrifft: Datumsfeld leer lassen |