Re: About "Allow VIEW/RULE recompilation when the underlying tables change"

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: suzhiyang <suzhiyang(at)gmail(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: About "Allow VIEW/RULE recompilation when the underlying tables change"
Date: 2009-12-19 03:17:43
Message-ID: 603c8f070912181917p333b25a3i9f368c160b5ae099@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Dec 18, 2009 at 9:58 PM, suzhiyang <suzhiyang(at)gmail(dot)com> wrote:
> I'm doing the Todo List's "Allow VIEW/RULE recompilation when the underlying
> tables change ". I've a very simple idea that I save the "create view"
> query_string in systable. When I found that I select from a view, I drop the
> view and recreate the view by execute the source query_string. Then go on
> execute this "select from a view" and will get the right answer. My problem
> is that how could I get the orginal query which user typed to postgres?
> Er, maybe drop and recreate the view is an ugly idea...Is there any better
> methods to do recompilation?

I am not sure what this TODO item is supposed to refer to, but saving
the query string and re-executing it is clearly not acceptable. What
if a column or table or function referenced in the query has been
renamed since the view/rule was created?

...Robert

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message suzhiyang 2009-12-19 03:25:22 Re: Re: [HACKERS] About "Allow VIEW/RULE recompilation when theunderlying tables change"
Previous Message Robert Haas 2009-12-19 03:15:50 Re: Largeobject Access Controls (r2460)