Re: pg_migrator and handling dropped columns - Mailing list pgsql-hackers

From Joshua D. Drake
Subject Re: pg_migrator and handling dropped columns
Date
Msg-id 1234464085.9467.73.camel@jd-laptop.pragmaticzealot.org
Whole thread Raw
In response to Re: pg_migrator and handling dropped columns  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: pg_migrator and handling dropped columns
Re: pg_migrator and handling dropped columns
List 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@jabber.postgresql.org  Consulting, Development, Support, Training  503-667-4564 -
http://www.commandprompt.com/ The PostgreSQL Company, serving since 1997
 



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: pg_migrator and handling dropped columns
Next
From: Tom Lane
Date:
Subject: Re: GIN fast insert