Re: BUG #15724: Can't create foreign table as partition
Etsuro Fujita <fujita.etsuro@lab.ntt.co.jp>
From: Etsuro Fujita <fujita.etsuro@lab.ntt.co.jp>
To: Stepan Yankevych <stepya@ukr.net>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Alvaro Herrera <alvherre@2ndquadrant.com>,
pgsql-bugs@lists.postgresql.org
Date: 2019-04-01T06:40:49Z
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
Commits
-
Fix partitioned index creation with foreign partitions
- 9653ca2197e2 11.5 landed
- 55ed3defc966 12.0 landed
-
Doc: Update documentation on partitioning vs. foreign tables.
- 7338ed28e2ec 11.3 landed
- 3e6b0c472942 12.0 landed