From: | Hannu Krosing <hannu(at)2ndQuadrant(dot)com> |
---|---|
To: | Vik Fearing <vik(dot)fearing(at)dalibo(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgreSQL(dot)org |
Subject: | Re: UPDATE SET (a,b,c) = (SELECT ...) versus rules |
Date: | 2014-06-17 12:38:40 |
Message-ID: | 53A036D0.5090100@2ndQuadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 06/17/2014 11:22 AM, Vik Fearing wrote:
> On 06/17/2014 09:43 AM, Hannu Krosing wrote:
>> On 06/14/2014 09:35 PM, Tom Lane wrote:
>>>> As I mentioned awhile ago, I'm thinking about implementing the
>>>> SQL-standard construct
>>>>
>>>> UPDATE foo SET ..., (a,b,...) = (SELECT x,y,...), ...
>>>>
>>>> I've run into a rather nasty problem, which is how does this interact
>>>> with expansion of NEW references in ON UPDATE rules?
>> 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.
But are there any cases, where UPDATE rules are created behind the scenes ?
--
Hannu Krosing
PostgreSQL Consultant
Performance, Scalability and High Availability
2ndQuadrant Nordic OÜ
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2014-06-17 12:47:41 | Re: UPDATE SET (a,b,c) = (SELECT ...) versus rules |
Previous Message | Amit Kapila | 2014-06-17 12:31:58 | Re: Wait free LW_SHARED acquisition - v0.2 |