| From: | PG Bug reporting form <noreply(at)postgresql(dot)org> |
|---|---|
| To: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Cc: | puneet(dot)orcl(at)gmail(dot)com |
| Subject: | BUG #17189: Index not created when primary key created |
| Date: | 2021-09-13 05:27:00 |
| Message-ID: | 17189-521a1b29d9727929@postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Bug reporting form | 2021-09-13 05:32:51 | BUG #17190: lock contention high in postgreSQL13.3 wrt GCC/llvm |
| Previous Message | Michael Paquier | 2021-09-13 04:37:21 | Re: BUG #17186: In connect.c, the lock connections_mutex is not correctly released(Line 463) at the return(Line 522) |