Re: BUG #15724: Can't create foreign table as partition - Mailing list pgsql-bugs

From Alvaro Herrera
Subject Re: BUG #15724: Can't create foreign table as partition
Date
Msg-id 20190329141050.GA22336@alvherre.pgsql
Whole thread Raw
In response to Re: BUG #15724: Can't create foreign table as partition  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re[2]: BUG #15724: Can't create foreign table as partition  (Stepan Yankevych <stepya@ukr.net>)
Re: BUG #15724: Can't create foreign table as partition  (Etsuro Fujita <fujita.etsuro@lab.ntt.co.jp>)
List 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



pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #15724: Can't create foreign table as partition
Next
From: Tom Lane
Date:
Subject: Re: BUG #15723: Export fails 'worker process died unexpectedly' but no error in pg_dump