Note that issuing warnings due to normal DML SQL queries is much more severe
than the typical DDL warnings. Many people have queries strewn throughout the
application so updating them may be a *lot* of work. And for an app issuing
hundreds or thousands of queries per minute (or even second) a warning could
effectively be a showstopper. It could require disabling all warnings in their
config to avoid filling their disk with Postgres logs in minutes.
I would suggest this warning be disable-able with a GUC variable. Otherwise
you're effectively giving no advance warning time to those users.
If postgres keeps advancing at the pace it's advancing now I might suggest
waiting two release cycles instead of just one. Judging by the mailing list it
seems a lot of users aren't able to keep up with the Postgres development team
and are often upgrading two versions at a time.
--
greg