Michael Paquier <michael.paqu...@gmail.com> writes: > Still, on back branches I think that it would be a good idea to have a > better error message for the ones that already throw an error, like > "trigger with OID %u does not exist". Switching from elog to ereport > would be a good idea, but wouldn't it be a problem to change what is > user-visible?
If we're going to touch this behavior in the back branches, I would vote for changing it the same as we do in HEAD. I do not think that making a user-visible behavior change in a minor release and then a different change in the next major is good strategy. But, given the relative shortage of complaints from the field, I'd be more inclined to just do nothing in back branches. There might be people out there with code depending on the current behavior, and they'd be annoyed if we change it in a minor release. regards, tom lane -- Sent via pgsql-hackers mailing list (firstname.lastname@example.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers