Message-ID: <5CA1B271.4040409@lab.ntt.co.jp>
Date: Mon, 01 Apr 2019 15:40:49 +0900
From: Etsuro Fujita <fujita.etsuro@lab.ntt.co.jp>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64;
 rv:11.0) Gecko/20120327 Thunderbird/11.0.1
MIME-Version: 1.0
Subject: Re: BUG #15724: Can't create foreign table as partition
References: <20190329135519.GA21373@alvherre.pgsql>
 <21389.1553868091@sss.pgh.pa.us>
 <1553876622.668408412.24u6zti5@frv53.fwdcdn.com>
In-Reply-To: <1553876622.668408412.24u6zti5@frv53.fwdcdn.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
To: Stepan Yankevych <stepya@ukr.net>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Alvaro Herrera <alvherre@2ndquadrant.com>,
        pgsql-bugs@lists.postgresql.org
Precedence: bulk

(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