| From: | Peter Geoghegan <peter(at)2ndquadrant(dot)com> |
|---|---|
| To: | Greg Stark <stark(at)mit(dot)edu> |
| Cc: | Josh Berkus <josh(at)agliodbs(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Deprecating RULES |
| Date: | 2012-10-17 18:07:04 |
| Message-ID: | CAEYLb_WeC-xbWNTpjKHHj09j-mEE3W16PHC215unZF7fn8qVGA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 17 October 2012 18:46, Greg Stark <stark(at)mit(dot)edu> wrote:
> I would suggest something like
>
> Warning: RULES are tricky to use correctly. They rewrite the original
> query into a new query before it is run and it is very hard to
> correctly anticipate and rewrite every possible input query into the
> desired result. There are also unexpected interactions with other
> components when RULES do something unexpected such as rewrite a single
> query to return two result sets.
+1 to that sort of wording.
--
Peter Geoghegan http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training and Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2012-10-17 18:13:13 | Re: Deprecating RULES |
| Previous Message | Peter Geoghegan | 2012-10-17 18:06:13 | Re: Deprecating RULES |