From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | jd(at)commandprompt(dot)com |
Cc: | Bruce Momjian <bruce(at)momjian(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:50:27 |
Message-ID: | 14802.1234464627@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
"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.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2009-02-12 18:52:45 | Re: GIN fast insert |
Previous Message | Bruce Momjian | 2009-02-12 18:47:12 | Re: pg_migrator and handling dropped columns |