Re: Deprecating RULES

From: Peter Geoghegan <peter(at)2ndquadrant(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>, Daniel Farina <daniel(at)heroku(dot)com>, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, Josh Berkus <josh(at)agliodbs(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Deprecating RULES
Date: 2012-10-12 19:10:18
Message-ID: CAEYLb_W5uNB9Ckt=ystQk_dL5rAOm15VAnizPfVYY1TTahV_8w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 12 October 2012 20:01, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> We know that rules are a bad fit for
> almost everything, *but we can't assume that our users all know that
> when it isn't even documented*.

I agree that we should document that rules are something that should
almost certainly be avoided. Up until recently, the advice surrounding
commit_delay in the docs said something practically indistinguishable
from "you don't want to use this". Why not do the same for rules?

--
Peter Geoghegan http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training and Services

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Stephen Frost 2012-10-12 19:17:28 Re: Truncate if exists
Previous Message Robert Haas 2012-10-12 19:07:18 Re: September 2012 commitfest