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

From Bruce Momjian
Subject Re: pg_migrator and handling dropped columns
Date
Msg-id 200902121949.n1CJnf211549@momjian.us
Whole thread Raw
In response to Re: pg_migrator and handling dropped columns  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tom Lane wrote:
> "Joshua D. Drake" <jd@commandprompt.com> writes:
> > On Thu, 2009-02-12 at 13:39 -0500, Tom Lane wrote:
> >> a long form only.  And probably not even list it in the user
> >> documentation.
> 
> > Why wouldn't we want to list it?
> 
> Because it's for internal use only.  Although the effect we're
> discussing here is relatively harmless, it seems possible that
> further down the road we might find a need for hacks that would
> render the output entirely unfit for ordinary dump purposes.
> I don't see a need to encourage people to play with fire.
> 
> It's hardly unprecedented for us to have undocumented internal
> options --- there are some in postgres.c for example.

The important point is that we add comments in the source code about why
it is undocumented.

--  Bruce Momjian  <bruce@momjian.us>        http://momjian.us EnterpriseDB
http://enterprisedb.com
 + If your life is a hard drive, Christ can be your backup. +


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: DISCARD ALL failing to acquire locks on pg_listen
Next
From: Robert Haas
Date:
Subject: Re: DISCARD ALL failing to acquire locks on pg_listen