Horton

Re: UPDATE SET (a,b,c) = (SELECT ...) versus rules

Hannu Krosing <hannu@2ndquadrant.com>

View thread View on postgr.es
From: Hannu Krosing <hannu@2ndQuadrant.com>
To: Vik Fearing <vik.fearing@dalibo.com>, Tom Lane <tgl@sss.pgh.pa.us>, pgsql-hackers@postgreSQL.org
Date: 2014-06-17T12:38:40Z
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Ü