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: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, stepya@ukr.net,
pgsql-bugs@lists.postgresql.org
Date: 2019-04-01T05:35:28Z
Lists: pgsql-bugs
(2019/03/29 23:10), Alvaro Herrera wrote: > On 2019-Mar-29, Tom Lane wrote: > >> Alvaro Herrera<alvherre@2ndquadrant.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
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