| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Zdenek Kotala <Zdenek(dot)Kotala(at)Sun(dot)COM> |
| Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pg_upgrade project status |
| Date: | 2009-01-27 14:47:07 |
| Message-ID: | 20090127144707.GF6444@alvh.no-ip.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Zdenek Kotala wrote:
> 2) pg_upgrade.sh
> http://archives.postgresql.org/pgsql-hackers/2008-12/msg00248.php
>
> Pg_upgrade.sh is shell script for catalog conversion. It works for
> 8.3->8.4 upgrade.
What's the reason this script uses a postmaster? It seems it would be
easier to control if you used a standalone backend (--single) for each
time you are piping stuff to psql. That would reduce the need to
configure authentication, hostnames, etc etc.
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Merlin Moncure | 2009-01-27 14:47:53 | Re: pg_upgrade project status |
| Previous Message | Ron Mayer | 2009-01-27 14:45:49 | Re: 8.4 release planning (was Re: [COMMITTERS] pgsql: Automatic view update rules) |