Re: Deprecating RULES - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: Deprecating RULES
Date
Msg-id CA+U5nMLUxo0ApVdhioFUx8+T7B7_6S7LAwbPxJktgmO5snZG_w@mail.gmail.com
Whole thread Raw
In response to Re: Deprecating RULES  (Josh Berkus <josh@agliodbs.com>)
Responses Re: Deprecating RULES  (Daniel Farina <daniel@heroku.com>)
Re: Deprecating RULES  (Josh Berkus <josh@agliodbs.com>)
List pgsql-hackers
On 11 October 2012 23:28, Josh Berkus <josh@agliodbs.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



pgsql-hackers by date:

Previous
From: Christopher Browne
Date:
Subject: Re: Deprecating RULES
Next
From: Christopher Browne
Date:
Subject: Re: [PATCH 8/8] Introduce wal decoding via catalog timetravel