From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | jd(at)commandprompt(dot)com, 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 19:49:41 |
Message-ID: | 200902121949.n1CJnf211549@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane wrote:
> "Joshua D. Drake" <jd(at)commandprompt(dot)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(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 | Alvaro Herrera | 2009-02-12 20:00:39 | Re: Synch Replication |
Previous Message | Tom Lane | 2009-02-12 19:29:56 | Re: DISCARD ALL failing to acquire locks on pg_listen |