| From: | Etsuro Fujita <fujita(dot)etsuro(at)lab(dot)ntt(dot)co(dot)jp> |
|---|---|
| To: | Stepan Yankevych <stepya(at)ukr(dot)net> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #15724: Can't create foreign table as partition |
| Date: | 2019-04-01 06:40:49 |
| Message-ID: | 5CA1B271.4040409@lab.ntt.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
(2019/03/30 1:25), Stepan Yankevych wrote:
>>> 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?
>
> Anyway it would be better to have no-op in 11.3 than having it not working.
>
> We just can put comment in the doc like.
>
> Foreign Server should take care about indexing foreign table as partition.
That might be OK, but before doing that, we would need to support eg,
unique constraints on foreign tables, so this seems more like a feature
than a fix to me.
Best regards,
Etsuro Fujita
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Langote | 2019-04-01 06:45:14 | Re: BUG #15724: Can't create foreign table as partition |
| Previous Message | PG Bug reporting form | 2019-04-01 06:32:07 | BUG #15725: pgAgent not working on Another database other than Postgres |