Re: Deprecating RULES - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: Deprecating RULES
Date
Msg-id CA+U5nML-k-rVewZEfpCPOYpBP7+HkXRtw9gnAEJPRfRve4VHzA@mail.gmail.com
Whole thread Raw
In response to Re: Deprecating RULES  (Josh Berkus <josh@agliodbs.com>)
List pgsql-hackers
On 17 October 2012 23:24, Josh Berkus <josh@agliodbs.com> wrote:

> I fact, I'll go further and say that I believe we will be deprecating
> RULEs eventually.  It's merely a question of how long that will take and
> what we need to document, announce and implement before then.
>
> I would tend to say "well, they're not hurting anyone, why not keep
> them?" Except that we're gathering an increasing number of features
> (RETURNING, FDWs, CTEs, Command triggers) which don't work well together
> with RULEs.  That puts us in danger of turning into MySQL ("Sorry, you
> can't use Full Text Search with transactions"), which is not a direction
> we want to go in.

I don't really understand. We *are* already in the position you say we
don't want to go towards. It's not a danger, its a current reality.

So what do we do? I've got the doc changes now. Let's agree the rest
of the plan...

-- Simon Riggs                   http://www.2ndQuadrant.com/PostgreSQL Development, 24x7 Support, Training & Services



pgsql-hackers by date:

Previous
From: "Kevin Grittner"
Date:
Subject: Re: Bugs in CREATE/DROP INDEX CONCURRENTLY
Next
From: Tom Lane
Date:
Subject: Re: Bugs in planner's equivalence-class processing