| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | stepya(at)ukr(dot)net, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #15724: Can't create foreign table as partition |
| Date: | 2019-03-29 14:01:31 |
| Message-ID: | 21389.1553868091@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> writes:
> On 2019-Mar-29, PG Bug reporting form wrote:
>> SQL Error [42809]: ERROR: cannot create index on foreign table "msg_json"
> Ah, this is because we try to propagate the index to the partition,
> which appears to be less than desirable. Maybe this patch fixes it? I
> have not tested it, only verified that it compiles.
Really, what *ought* to happen in such a case is that the FDW gets
told about the command and has the opportunity to try to do something
corresponding to making an index. But that smells like a new feature
rather than a bug fix.
I'm not sure that just forcing the case to be a no-op is wise.
What if the index is supposed to be UNIQUE?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2019-03-29 14:10:50 | Re: BUG #15724: Can't create foreign table as partition |
| Previous Message | Alvaro Herrera | 2019-03-29 13:55:19 | Re: BUG #15724: Can't create foreign table as partition |