Re: BUG #15724: Can't create foreign table as partition
Alvaro Herrera <alvherre@2ndquadrant.com>
From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: stepya@ukr.net, pgsql-bugs@lists.postgresql.org
Date: 2019-03-29T14:10:50Z
Lists: pgsql-bugs
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" > > > 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. ENOTIME to get it done for pg12 I suppose (I don't know a thing about postgres_fdw or the FDW API layer). > 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. -- Álvaro Herrera https://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
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