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

Поиск
Список
Период
Сортировка
От Puneet Sharma
Тема Re: BUG #17189: Index not created when primary key created
Дата
Msg-id CALETbT9ZZPyLAc4+OU=hD5xP0c3iywFq0n-DqoOYwjVEOq8aGg@mail.gmail.com
обсуждение исходный текст
Ответ на Re: BUG #17189: Index not created when primary key created  ("David G. Johnston" <david.g.johnston@gmail.com>)
Ответы Re: BUG #17189: Index not created when primary key created  (Jaime Casanova <jcasanov@systemguards.com.ec>)
Список pgsql-bugs
Дерево обсуждения
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.g.johnston@gmail.com> wrote:
On Monday, September 13, 2021, PG Bug reporting form <noreply@postgresql.org> wrote:
The following bug has been logged on the website:

Bug reference:      17189
Logged by:          Puneet Sharma
Email address:      puneet.orcl@gmail.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

В списке pgsql-bugs по дате отправления:

Предыдущее
От: Alexander Lakhin
Дата:
Сообщение: Re: BUG #17197: Assert failed on inserting index tuples after VACUUM
Следующее
От: Magnus Hagander
Дата:
Сообщение: Re: BUG #17198: Planning time too high when execute query on standby cluster