| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Josh Berkus <josh(at)agliodbs(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Deprecating RULES |
| Date: | 2012-10-11 22:39:00 |
| Message-ID: | CA+U5nMLUxo0ApVdhioFUx8+T7B7_6S7LAwbPxJktgmO5snZG_w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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).
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christopher Browne | 2012-10-11 22:41:00 | Re: [PATCH 8/8] Introduce wal decoding via catalog timetravel |
| Previous Message | Christopher Browne | 2012-10-11 22:32:38 | Re: Deprecating RULES |