Re: UPDATE SET (a,b,c) = (SELECT ...) versus rules - Mailing list pgsql-hackers

From Andres Freund
Subject Re: UPDATE SET (a,b,c) = (SELECT ...) versus rules
Date
Msg-id 20140617134805.GD18143@awork2.anarazel.de
Whole thread Raw
In response to Re: UPDATE SET (a,b,c) = (SELECT ...) versus rules  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On 2014-06-17 09:46:13 -0400, Tom Lane wrote:
> Andres Freund <andres@2ndquadrant.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.

IMO INSTEAD triggers pretty much are that. We only need to make them
work for normal relations as well (partitioning!) and we're pretty much
there.

Greetings,

Andres Freund

-- Andres Freund                       http://www.2ndQuadrant.com/PostgreSQL Development, 24x7 Support, Training &
Services



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: UPDATE SET (a,b,c) = (SELECT ...) versus rules
Next
From: Robert Haas
Date:
Subject: Re: avoiding tuple copying in btree index builds