Re: pg_migrator and handling dropped columns

From: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Bruce Momjian <bruce(at)momjian(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Peter Eisentraut <peter_e(at)gmx(dot)net>, Zdenek Kotala <Zdenek(dot)Kotala(at)Sun(dot)COM>
Subject: Re: pg_migrator and handling dropped columns
Date: 2009-02-12 18:41:25
Message-ID: 1234464085.9467.73.camel@jd-laptop.pragmaticzealot.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, 2009-02-12 at 13:39 -0500, Tom Lane wrote:

> Right, that's what I meant --- do all the work within pg_dump.
>
> > Is this acceptable to everyone? We could name the option
> > -u/--upgrade-compatible.
>
> If the switch is specifically for pg_upgrade support (enabling this as
> well as any other hacks we find necessary), which seems like a good
> idea, then don't chew up a short option letter for it. There should be
> a long form only. And probably not even list it in the user
> documentation.

Why wouldn't we want to list it?

Joshua D. Drake

>
> regards, tom lane
>
--
PostgreSQL - XMPP: jdrake(at)jabber(dot)postgresql(dot)org
Consulting, Development, Support, Training
503-667-4564 - http://www.commandprompt.com/
The PostgreSQL Company, serving since 1997

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2009-02-12 18:42:11 Re: GIN fast insert
Previous Message Tom Lane 2009-02-12 18:39:06 Re: pg_migrator and handling dropped columns