| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andres Freund <andres(at)2ndquadrant(dot)com> |
| Cc: | Vik Fearing <vik(dot)fearing(at)dalibo(dot)com>, Hannu Krosing <hannu(at)2ndquadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: UPDATE SET (a,b,c) = (SELECT ...) versus rules |
| Date: | 2014-06-17 13:46:13 |
| Message-ID: | 16542.1403012773@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andres Freund <andres(at)2ndquadrant(dot)com> writes:
> On 2014-06-17 11:22:17 +0200, Vik Fearing wrote:
>> On 06/17/2014 09:43 AM, Hannu Krosing wrote:
>>> Was'nt there a plan (consensus?) about deprecating rules altogether ?
>> I believe that was just for user access to them, ie CREATE RULE. I
>> don't think there was ever question of purging them from the code base.
> I don't think any such concensus has been made? I wish it were, but the
> last discussions about it imo ended quite differently.
Yeah, I don't think there's any prospect of removing them in the near
future. We'd need a (better-designed) replacement feature first.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2014-06-17 13:48:05 | Re: UPDATE SET (a,b,c) = (SELECT ...) versus rules |
| Previous Message | Tom Lane | 2014-06-17 13:40:43 | Re: How to implement the skip errors for copy from ? |