| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
| Cc: | Haribabu Kommi <kommi(dot)haribabu(at)gmail(dot)com>, brown(at)fastmail(dot)com, "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: BUG #13741: vacuumdb does not accept valid password |
| Date: | 2015-11-12 21:08:50 |
| Message-ID: | 20151112210850.GP614468@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
Michael Paquier wrote:
> OK, so attached is a patch aimed at master and 9.5. I reused the
> suggestion of Haribabu to not rely completely on the maintenance
> database after testing with a couple of database, some of them using
> md5 and others trust. That's just more portable this way, and user
> just needs to specify the password once to be done even with vacuumdb
> --all.
Thanks, pushed a slightly tweaked version. If you can please verify
that I didn't break anything, it'd be great.
FWIW I think the mode that generated the most connections is -jN --all
--analyze-in-stages. For additional annoyance, one sets up the
"postgres" database with trust auth and others with md5. All the cases
I tried only get a single prompt now.
Thanks Eric for reporting the problem and Haribabu and Michael for
patching.
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2015-11-12 21:17:10 | Re: BUG #13741: vacuumdb does not accept valid password |
| Previous Message | manu | 2015-11-12 19:57:35 | BUG #13774: upgrade from 9.1 to 9.4 'succeeds' without enough disk space |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2015-11-12 21:09:40 | Re: psql: add \pset true/false |
| Previous Message | Tom Lane | 2015-11-12 21:01:08 | Re: Inaccurate results from numeric ln(), log(), exp() and pow() |