| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Daniel Cristian Cruz <danielcristian(at)gmail(dot)com>, pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: BUG #6050: Dump and restore of view after a schema change: can't restore the view |
| Date: | 2011-06-07 15:41:22 |
| Message-ID: | 14241.1307461282@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> If your point here is that you don't want to spend time hacking on
> this because it's a fairly marginal feature and therefore not terribly
> high on your priority list, I can understand that. But if you're
> actually defending the current implementation, I'm going to have to
> respectfully disagree. It's broken, and it sucks, and this is not the
> first complaint we've had about it.
The spec's definition of USING is broken and sucky, and we're
implementing it as best we can. I don't feel a need to invent
strange nonstandard behavior to work around the fact that USING
is fragile *by definition*. Complain to the standards committee
about that.
(Question: would you also have us try to work around the fact that
USING stops working if you rename one of the join columns?)
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Daniel Cristian Cruz | 2011-06-07 15:43:37 | Re: BUG #6050: Dump and restore of view after a schema change: can't restore the view |
| Previous Message | Tom Lane | 2011-06-07 15:33:29 | Re: ON DELETE CASCADE with multiple paths in PostgreSQL 9.x |