Re: BUG #17189: Index not created when primary key created

Hi David,

Is it different from postgres 12 version and postgres 12.8 version.

When we are creating composite primary key default constraint has been
created but not index like oracle.

Regards
Puneet kumar

On Mon, 13 Sep 2021 at 6:26 PM, David G. Johnston <
david(dot)g(dot)johnston(at)gmail(dot)com> wrote:

> On Monday, September 13, 2021, PG Bug reporting form <
> noreply(at)postgresql(dot)org> wrote:
>
>> The following bug has been logged on the website:
>>
>> Bug reference: 17189
>> Logged by: Puneet Sharma
>> Email address: puneet(dot)orcl(at)gmail(dot)com
>> PostgreSQL version: 12.0
>> Operating system: Linux
>> Description:
>>
>> I have created the composite primary key which is created successfully
>> but i
>> am not getting the index against the primary key.
>>
>> When i created a select query and includes the primary key column it is
>> going with full table scan. Even i am creating an index on the columns it
>> is
>> also going with full table scan.
>
>
> This isn’t a bug, it did create the indexes. The fact that a particular
> query choose not to use them is not evidence to the contrary.
>
> David J.
>
>
--

Regards
Puneet Kumar