From: | Etsuro Fujita <fujita(dot)etsuro(at)lab(dot)ntt(dot)co(dot)jp> |
---|---|
To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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-04-01 05:35:28 |
Message-ID: | 5CA1A320.4050707@lab.ntt.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
(2019/03/29 23:10), Alvaro Herrera wrote:
> On 2019-Mar-29, Tom Lane wrote:
>
>> 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"
>> 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.
Interesting!
>> corresponding to making an index. But that smells like a new feature
>> rather than a bug fix.
> ENOTIME to get it done for pg12 I suppose (I don't know a thing about
> postgres_fdw or the FDW API layer).
Yeah, I think so.
>> 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?
>
> Hmm, good point, that should be disallowed too.
Agreed.
Best regards,
Etsuro Fujita
From | Date | Subject | |
---|---|---|---|
Next Message | Etsuro Fujita | 2019-04-01 06:01:50 | Re: BUG #15724: Can't create foreign table as partition |
Previous Message | Erik Rijkers | 2019-03-30 08:26:57 | test - please ignore |