Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> On tor, 2010-10-14 at 08:50 -0400, Robert Haas wrote:
>> Still, I don't think it would be unreasonable to add a note to the
>> prior-release documentation saying - hey, these functions exist. They
>> are for internal use only, and do not exist in later versions. Don't
>> use 'em. Now, how many people will actually see that note? Probably
>> not many. But it wouldn't bother me to have it there.
> Just like there is a philosophical argument against changing the release
> notes after the release, there is an argument against changing a past
> release to "retroactively predict" how future releases behave. We have
> made exceptions to both points on occasion, but usually only for
> critical upgrade-related issues.
I would put this whole issue in the category of "if you use undocumented
features, you should not be surprised when they undocumentedly break".
There are many many places where it's possible to see undocumented
implementation details in Postgres. If we put in release-note warnings
every time we changed one of those details, the release notes would be
twice as long and half as useful as they are now.
regards, tom lane
In response to
pgsql-docs by date
|Next:||From: Tom Lane||Date: 2010-10-14 14:38:11|
|Subject: Re: Documenting removal of nonnullvalue() and friends |
|Previous:||From: Josh Kupershmidt||Date: 2010-10-14 14:29:42|
|Subject: Re: Documenting removal of nonnullvalue() and friends|