Re: BUG #15724: Can't create foreign table as partition

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: Amit Langote <amitlangote09(at)gmail(dot)com>
Cc: Pavan Deolasee <pavan(dot)deolasee(at)gmail(dot)com>, stepya(at)ukr(dot)net, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: BUG #15724: Can't create foreign table as partition
Date: 2019-06-26 20:18:43
Message-ID: 20190626201843.GA18542@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-bugs

On 2019-Jun-26, Amit Langote wrote:

> On Tue, Jun 25, 2019 at 9:57 PM Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> wrote:

> > Because if you do that, you might build a few indexes on regular
> > partitions before coming across a foreign one, which is very unfriendly.
> > I'll add a comment to this effect.
> Hmm, why would other partitions be involved?
> AttachPartitionEnsureIndexes() only considers the partition being
> attached, like DefineRelation only considers the partition being
> created.

Sorry, I meant other *indexes*. You might build a few regular
(non-unique) indexes before coming across a unique index, at which point
you throw the error.

Álvaro Herrera
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2019-06-26 21:06:47 Re: Re: Querying foreign table with SP-GiST index results in “ERROR: cache lookup failed for type 0”
Previous Message PG Bug reporting form 2019-06-26 16:07:08 BUG #15876: A SUGGESTION