Re: Deprecating RULES

On Thu, Oct 11, 2012 at 3:39 PM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
> On 11 October 2012 23:28, Josh Berkus <josh(at)agliodbs(dot)com> wrote:
>>
>>>> For 9.3, I suggest we create a DDL trigger by default which prevents
>>>> RULEs and throws an ERROR that explains they are now deprecated.
>>
>> Well, even if we were considering this, the sequence would need to be:
>>
>> 1. Announce in 9.3 that RULES will be going away RSN.
>> 2. In 9.4, send a warning every time someone loads/edits a user-defined
>> RULE.
>> 3. In 10.0, get rid of CREATE RULE.
>
> With the DDL trigger, we're able to do that faster. The idea is you
> can still delete it if you need compatibility, so we get the message
> across without an extra release and without an annoying GUC (etc).

This seems sane to me. The deprecation of standard-conforming strings
was very smooth in our experience, because it seems like practically
every client has adjusted in that long deprecation period. By
contrast, the sudden bytea format change was not nearly so smooth --
it bit a lot of people and we have had to change our configuration to
override Postgres's default (which we are loathe to do) to the old
encoding as our platform-default when vending databases until we can
age out all older libpqs, which is going to take quite some time.

So, apparently, griping continuously in the logs does get the job done.

--
fdr