| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | jd(at)commandprompt(dot)com |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(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:47:12 |
| Message-ID: | 200902121847.n1CIlCd23956@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Joshua D. Drake wrote:
> 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?
Because it is for internal use by upgrade utilities, not for user use.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2009-02-12 18:50:27 | Re: pg_migrator and handling dropped columns |
| Previous Message | Bruce Momjian | 2009-02-12 18:46:42 | Re: pg_migrator and handling dropped columns |