Sachin Kotwal wrote:
> 3. Notify or highlight these changes in release notes because this can
> break some existing tools and user code.
Notifying people when their tools no longer work with a new server is
not the problem; they figure that out pretty quickly once they try the
new version. The problem is that if you change any names, the
application developers need to provide version-specific queries that
work across all the PG versions they want to support. That leads to
some pretty horrible code, annoyed developers, bad publicity for Pg
("you guys don't love your app developers!"), etc.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
