| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | pgsql-hackers(at)lists(dot)postgresql(dot)org,Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>,Yugo Nagata <nagata(at)sraoss(dot)co(dot)jp> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Fix to not check included columns in ANALYZE on indexes |
| Date: | 2018-06-28 23:22:55 |
| Message-ID: | D0EAA77B-1F8F-4D1A-B8E0-576D568D92A2@anarazel.de |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On June 28, 2018 4:18:36 PM PDT, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>Yugo Nagata <nagata(at)sraoss(dot)co(dot)jp> writes:
>> I found that both key columns and included columns are checked when
>analyze
>> is run on indexes. This is almost harmless because non-expression
>columns
>> are not processed. However, this check is obviously unnecessary and
>we
>> can fix this to not check included columns. If we decide to support
>expressions
>> in included columns in future, this must be fixed eventually.
>
>AFAICS, we'd just have to revert this patch later, so I don't see
>much value in it.
>
>Also, is it really true that we don't support included expression
>columns now? In what way would that not be a bug?
I don't think IOS supports expression columns, right? Away from code for a bit, so can't check. If indeed true, there'd be little point in allowing it, right?
Andres
Andres
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2018-06-28 23:28:39 | Re: Fix to not check included columns in ANALYZE on indexes |
| Previous Message | David G. Johnston | 2018-06-28 23:22:15 | Re: CREATE TABLE .. LIKE .. EXCLUDING documentation |