From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
Cc: | Josh Berkus <josh(at)agliodbs(dot)com>, Daniel Farina <daniel(at)heroku(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Deprecating RULES |
Date: | 2012-10-19 19:55:10 |
Message-ID: | CA+TgmoZxDN7tN+8HtmXDztmL43Wne383JB2VP4wU9oXd0fxE9A@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, Oct 19, 2012 at 10:29 AM, Andrew Dunstan <andrew(at)dunslane(dot)net> wrote:
> As you can see, in the case of rewrite it takes us back 7 1/2 years. I know
> this is a *very* rough measure, but it still tends to indicate to me that
> the maintenance burden isn't terribly high.
That's a pretty neat one-liner. However... in my view, the real cost
of rules is that they are hard to support as we add new features to
SQL. I believe we already decided to punt on making them work with
CTEs... and maybe one other case? I don't really remember the details
any more, but presumably this will come up again with MERGE, and
perhaps other cases...
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2012-10-19 20:02:52 | Re: hash_search and out of memory |
Previous Message | Hitoshi Harada | 2012-10-19 19:31:41 | Re: hash_search and out of memory |