Tom Lane wrote: > Bruce Momjian <br...@momjian.us> writes: > > Tom Lane wrote: > >> (4) add a switch to pg_dump to include dropped columns in its > >> schema output and then drop them. This seems far more maintainable > >> than writing separate code that tries to parse the output. > > > I assume I would also drop the column in the pg_dump output. > > 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.
OK, works for me; any objections from anyone? -- Bruce Momjian <br...@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + If your life is a hard drive, Christ can be your backup. + -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
