| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | "puneet(dot)orcl(at)gmail(dot)com" <puneet(dot)orcl(at)gmail(dot)com>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: BUG #17189: Index not created when primary key created |
| Date: | 2021-09-13 12:56:19 |
| Message-ID: | CAKFQuwYf-rNmNenHsT3Vy=v-OMkDtin25yaxcSNwAbxmRki+tA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2021-09-13 13:20:37 | Re: pg_upgrade test for binary compatibility of core data types |
| Previous Message | PG Bug reporting form | 2021-09-13 12:27:41 | BUG #17191: Docker / buildx issue - An image created with buildx requires to set custom PGDATA location |