| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: new --maintenance-db options |
| Date: | 2012-06-25 18:49:24 |
| Message-ID: | 1340650078-sup-1192@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Excerpts from Robert Haas's message of lun jun 25 11:57:36 -0400 2012:
> Really, I think
> pg_upgrade needs this option too, unless we're going to kill the
> problem at its root by providing a reliable way to enumerate database
> names without first knowing the name one that you can connect to.
I think pg_upgrade could do this one task by using a standalone backend
instead of a full-blown postmaster. It should be easy enough ...
--
Álvaro Herrera <alvherre(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Grittner | 2012-06-25 18:50:54 | Re: Catalog/Metadata consistency during changeset extraction from wal |
| Previous Message | Andres Freund | 2012-06-25 18:19:47 | Re: Catalog/Metadata consistency during changeset extraction from wal |