| From: | Thom Brown <thom(at)linux(dot)com> |
|---|---|
| To: | Kevin Grittner <kgrittn(at)ymail(dot)com> |
| Cc: | Noah Misch <noah(at)leadboat(dot)com>, Kevin Grittner <kgrittn(at)mail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Marko Tiikkaja <pgmail(at)joh(dot)to>, Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Materialized views WIP patch |
| Date: | 2013-02-17 20:23:57 |
| Message-ID: | CAA-aLv5K9LkdTjYbrB=QxqKDE4TA4nyvg_t1oc2ZF_yAfq7s3Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
On 16 February 2013 01:01, Kevin Grittner <kgrittn(at)ymail(dot)com> wrote:
> Unless something else comes up in review or I get feedback to the
> contrary I plan to deal with the above-mentioned issues and commit
> this within a week or two.
At the moment it's not possible to rename a column without using ALTER
TABLE on an MV.
Also, shouldn't we have the ability to set the collation on a column of the MV?
And the inconsistency between regular views and MVs is still present,
where MVs always dump with column parameters in their definition, and
views never do. Not a show-stopper, but curious nonetheless.
--
Thom
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2013-02-18 04:47:25 | pgsql: Add ALTER ROLE ALL SET command |
| Previous Message | Kevin Grittner | 2013-02-17 15:13:27 | Re: Materialized views WIP patch |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2013-02-17 20:53:44 | Re: JSON Function Bike Shedding |
| Previous Message | Andres Freund | 2013-02-17 20:20:14 | Re: overlapping strncpy/memcpy errors via valgrind |