| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Is user_catalog_table sensible for matviews? |
| Date: | 2016-11-09 17:55:51 |
| Message-ID: | CA+TgmoYfxfFMjZB1amHEiGdL4KJb8Htj0fQWrRdxWL1bTg_G7Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Nov 9, 2016 at 12:17 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> The system will let you set the "user_catalog_table" reloption to "true"
> on a materialized view. Is this sensible, or is it a bug caused by the
> fact that reloptions.c fails to distinguish matviews from heaps at all?
>
> If it is sensible, then I broke it in e3e66d8a9 ...
I can understand what that combination of opens would mean from a
semantic point of view, so I don't think it's insensible. However, it
doesn't seem like an important combination to support, and I suspect
that the fact that we did was accidental.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2016-11-09 17:58:54 | Re: Incorrect overflow check condition for WAL segment size |
| Previous Message | Markus Nullmeier | 2016-11-09 17:54:58 | Re: Incorrect overflow check condition for WAL segment size |