| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | lalbin(at)fhcrc(dot)org |
| Cc: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: BUG #7553: Un-executable view definitions in pg_catalog.pg_views in versions 8.3.x-9.2.0 |
| Date: | 2012-09-18 16:41:18 |
| Message-ID: | 21842.1347986478@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
lalbin(at)fhcrc(dot)org writes:
> I have run across a situation where we are changing schema and table names
> that a view references. The view is still viewable with a select statement
> but if you try and execute the view definition contained within the
> pg_catalog.pg_views, then it fails.
This appears to be a variant of the what-alias-to-use-after-a-rename
problem that we were discussing last winter:
http://archives.postgresql.org/message-id/29791.1327718297@sss.pgh.pa.us
That thread kinda died off after coming to the conclusion that there
isn't a simple, obviously correct solution. The code's current behavior
is definitely wrong in the face of renames, but I don't want to change
it in a way that just moves the failure cases elsewhere (which is what
would happen for any of the proposals made in the thread :-().
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | tom Tom | 2012-09-18 17:36:56 | Re: BUG #7550: NULL result when coercing a subquery result into an array |
| Previous Message | Devrim GÜNDÜZ | 2012-09-18 15:57:08 | Re: BUG #7555: fail to install ora2pg through rhel5 postgresql repo (depsolv issues) |