>> 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
3. In 10.0, get rid of CREATE RULE.
> This is utter nonsense. We can't deprecate them until we have a
> substitute that is better. If you want to get rid of rules, build the
> replacement; don't just try to be a pain in the ass to users.
I was thinking that this should start with making a list of all of the
things you can currently do with RULEs and making sure that we have an
equivalent. When it actually comes time to dump RULEs entirely, we
would also need docs on how to migrate existing RULEs to the new
equivalents (e.g. rewriting a RULE as a view or a trigger).
Wiki page, anyone?
PostgreSQL Experts Inc.
In response to
pgsql-hackers by date
|Next:||From: Christopher Browne||Date: 2012-10-11 22:32:38|
|Subject: Re: Deprecating RULES|
|Previous:||From: Josh Berkus||Date: 2012-10-11 22:27:27|
|Subject: Re: [PATCH 8/8] Introduce wal decoding via catalog timetravel|