From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | ash <ash(at)commandprompt(dot)com>, Stephen Frost <sfrost(at)snowman(dot)net>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Re-create dependent views on ALTER TABLE ALTER COLUMN ... TYPE? |
Date: | 2014-06-02 14:21:55 |
Message-ID: | 11437.1401718915@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> On Mon, Jun 2, 2014 at 8:52 AM, ash <ash(at)commandprompt(dot)com> wrote:
>> Should this fail, the user will have to work around it, but most of the
>> time it could just work.
> You're either missing or choosing to ignore the point that I'm making,
> which is that we *don't have* the text form of the view anywhere.
Even if we did, I don't think it'd affect this decision.
The real problem in my mind is one of user expectations. If the database
silently does something behind your back, people expect that that action
will be *right* and they don't have to worry about it. I don't think
that automatically reparsing views has much chance of clearing that bar.
In much simpler, non-extensible SQL systems it could probably work, but
for better or worse Postgres has gone all-in on datatype extensibility.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2014-06-02 14:22:49 | Re: Jsonb: jbvBinary usage in the convertJsonbValue? |
Previous Message | Alvaro Herrera | 2014-06-02 14:10:41 | Re: BUG #8673: Could not open file "pg_multixact/members/xxxx" on slave during hot_standby |