Re: dropping column prevented due to inherited index

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Amit Langote <amitlangote09(at)gmail(dot)com>
Cc: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Ashutosh Sharma <ashu(dot)coek88(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: Re: dropping column prevented due to inherited index
Date: 2019-10-11 08:52:57
Message-ID: 20191011085257.GD2373@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Oct 11, 2019 at 04:23:51PM +0900, Amit Langote wrote:
> Thanks. The index on b is not really necessary for testing because it
> remains unaffected, but maybe it's fine.

That's on purpose. Any more comments?
--
Michael

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Nikolay Shaplov 2019-10-11 10:37:59 Re: [PATCH] use separate PartitionedRelOptions structure to store partitioned table options
Previous Message David Rowley 2019-10-11 08:47:51 Re: BRIN index which is much faster never chosen by planner