From: | Andres Freund <andres(at)anarazel(dot)de> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Is user_catalog_table sensible for matviews? |
Date: | 2016-11-10 11:54:12 |
Message-ID: | 20161110115412.qp6yhslhwurxue4a@alap3.anarazel.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 2016-11-09 12:55:51 -0500, Robert Haas wrote:
> 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.
I don't see it as being important either. I suspect we intentionally
didn't exclude it, but less because of a use-case and more because there
didn't seem to be a need to.
Andres
From | Date | Subject | |
---|---|---|---|
Next Message | Dean Rasheed | 2016-11-10 11:56:30 | Re: Improving RLS planning |
Previous Message | Kyotaro HORIGUCHI | 2016-11-10 10:33:06 | Re: Floating point comparison inconsistencies of the geometric types |