Tom Lane wrote:
> Andreas Pflug <pgadmin@pse-consulting.de> writes:
>
>>Yes, some kind of information "initdb required because column xxx was
>>dropped" would be helpful. When scanning the whole beta4-to-beta5 file,
>>you'd easily miss the consequence of the 2004-11-05 patch ("remove
>>concept of a schema having an associated tablespace").
>
>
> We do ordinarily say "initdb required" in the changelog message when it
> applies. I unaccountably failed to say that in this particular
> commit message. Entirely my fault, and I do apologize again.
No need for apologies, we're not seeking for the one to blame.
What I'd like to emphasize is that some kind of announcement mechanism
for those of us who code system schema and version dependent stuff is
desirable, exceeding commit messages. psql issues are discussed
integratedly on pgsql-hackers; usually, schema changes are tracked
immediately within the very same cvs commit, making psql a privileged
tool (to me, it's just another tool). Additional tools require the same
attention by maintainers, but it's much harder for them.
Multiversion tools are even more challenging, maintainance not made
easier by the documentation that won't mark version differences
(something like "this feature was added in ..." would be really nice).
If we had some "admin-announcement@pgsql.org" list anybody who noticed
some schema relevant change could post there (e.g. usually Dave, Chris
or me will notice sooner or later) instead of just fixing the stuff
silently for his own tool only. Postings by committers who think "hey,
some tool maintainers might want to know this" welcome too.
Regards,
Andreas