| From: | Yugo Nagata <nagata(at)sraoss(dot)co(dot)jp> |
|---|---|
| To: | Yugo Nagata <nagata(at)sraoss(dot)co(dot)jp> |
| Cc: | Andrey Borodin <x4mmm(at)yandex-team(dot)ru>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Aditya Toshniwal <aditya(dot)toshniwal(at)enterprisedb(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: [PG-11] Potential bug related to INCLUDE clause of CREATE INDEX |
| Date: | 2018-07-12 07:20:13 |
| Message-ID: | 20180712162013.b74e2166.nagata@sraoss.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, 12 Jul 2018 15:58:08 +0900
Yugo Nagata <nagata(at)sraoss(dot)co(dot)jp> wrote:
> Yes, more simplly, the following query also works;
>
> CREATE INDEX ON test((i)) INCLUDE (i);
>
> However, a problem is that when we use pg_dump for the database, this generate the following query
>
> CREATE INDEX test_i_i1_idx ON public.test USING btree (i) INCLUDE (i);
>
> Of cause, this causes the "must not intersect" error, and we cannot restore this dump.
>
> To fix this, we agree with Tom about getting rid of "must not intersect" restriction.
> A patch is attached for this
Should we add this to PG11 open items?
--
Yugo Nagata <nagata(at)sraoss(dot)co(dot)jp>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2018-07-12 07:33:54 | pgsql: Allow using the updated tuple while moving it to a different par |
| Previous Message | Yugo Nagata | 2018-07-12 06:58:08 | Re: [PG-11] Potential bug related to INCLUDE clause of CREATE INDEX |