| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Daniel Farina <daniel(at)heroku(dot)com>, darren(at)darrenduncan(dot)net |
| Cc: | Peter Geoghegan <peter(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Deprecating RULES |
| Date: | 2012-10-17 09:48:39 |
| Message-ID: | CA+U5nMJyzFCGtSADx7ocxi6ezYm0OOyRrE04dMxMO0B=4yKWbw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 12 October 2012 10:08, Daniel Farina <daniel(at)heroku(dot)com> wrote:
> On Thu, Oct 11, 2012 at 11:55 PM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
>> As regards cost/benefit analysis, this is a low importance feature,
>> but then that is why I proposed a low effort fix that is flexible to
>> the needs of users affected.
>
> Is there any feature that is more loathed and more narrowly used than
> rules?
I doubt it.
Would you or someone else be able to come up with some words of
caution for us to put in the manual that would be helpful to
developers?
There isn't even a list of caveats for rules.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dimitri Fontaine | 2012-10-17 10:21:25 | Re: Global Sequences |
| Previous Message | chinnaobi | 2012-10-17 09:38:51 | Re: How to avoid base backup in automated failover |