Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> On Sun, Jul 1, 2012 at 6:35 PM, Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com> wrote:
>> Basically what it does is this: in the first stage of query rewriting,
>> just after any non-SELECT rules are applied, the new code kicks in -
>> if the target relation is a view, and there were no unqualified
>> INSTEAD rules, and there are no INSTEAD OF triggers, it tests if ...

>> The consensus last time seemed to be that backwards compatibility
>> should be offered through a new GUC variable to allow this feature to
>> be disabled globally, which I've not implemented yet.

> I think the backward-compatibility concerns with this approach would
> be much less than with the previously-proposed approach, so I'm not
> 100% sure we need a backward compatibility knob.

If the above description is correct, the behavior is changed only in
cases that previously threw errors, so I tend to agree that no
"backwards compatibility knob" is needed.

			regards, tom lane

In response to

• Re: Proof of concept: auto updatable views at 2012-07-02 20:27:25 from Robert Haas

Responses

• Re: Proof of concept: auto updatable views at 2012-07-03 06:53:02 from Dean Rasheed

pgsql-hackers by date

Next:	From: Robert Haas	Date: 2012-07-02 20:34:11
	Subject: Re: Event Triggers reduced, v1
Previous:	From: Alexander Korotkov	Date: 2012-07-02 20:33:11
	Subject: Re: Patch: add conversion from pg_wchar to multibyte