Re: [GENERAL] Simple Query not using Primary Key Index

Here is the dumb part  Turns out what caused my confusion that I had an identical table in another schema and I used different sessions with a different search_path with different results. Thank you for helping me on this. On Mon, Feb 6, 2017, 7:03 PM Vitaly Burovoy

Re: [GENERAL] Simple Query not using Primary Key Index

On 2/6/17, Aron Podrigal wrote: > In general, I do not understand why a PK index should not be used when the > query can be satisfied by the index itself. Can anyone give some reason to > this? > > On Mon, Feb 6, 2017, 6:29 PM Aron Podrigal >

Re: [GENERAL] Simple Query not using Primary Key Index

On Mon, Feb 6, 2017 at 4:16 PM, Podrigal, Aron wrote: > Hi, > > I noticed when I do a simple SELECT id FROM mytable WHERE id = > 'cb81d070-4213-465f-b32e-b8db43b83a25'::UUID Postgres does not use the > primary key index and opts for a Seq Scan. > > I of course did

Re: [GENERAL] Simple Query not using Primary Key Index

After resetting all statistics it still opts for a Seq Scan. I went ahead to test with creating another table and querying that, and it shows on that test table to be using the index. So I wonder if there is anything else that may effect the planner. is there a way I can dog into this and see the

Re: [GENERAL] Simple Query not using Primary Key Index

In general, I do not understand why a PK index should not be used when the query can be satisfied by the index itself. Can anyone give some reason to this? On Mon, Feb 6, 2017, 6:29 PM Aron Podrigal wrote: > EXPLAIN ANALYZE does not tell me much. It doesn't say why the

Re: [GENERAL] Simple Query not using Primary Key Index

On 2/6/17, Podrigal, Aron wrote: > Hi, > > I noticed when I do a simple SELECT id FROM mytable WHERE id = > 'cb81d070-4213-465f-b32e-b8db43b83a25'::UUID Postgres does not use the > primary key index and opts for a Seq Scan. > > I of course did VACUUM ANALYZE and I have

Re: [GENERAL] Simple Query not using Primary Key Index

EXPLAIN ANALYZE does not tell me much. It doesn't say why the planner opts for not using the Primary key index. On Mon, Feb 6, 2017, 6:23 PM Alban Hertroys wrote: > > > On 7 Feb 2017, at 0:16, Podrigal, Aron wrote: > > > > Hi, > > > > I noticed

Re: [GENERAL] Simple Query not using Primary Key Index

> On 7 Feb 2017, at 0:16, Podrigal, Aron wrote: > > Hi, > > I noticed when I do a simple SELECT id FROM mytable WHERE id = > 'cb81d070-4213-465f-b32e-b8db43b83a25'::UUID Postgres does not use the > primary key index and opts for a Seq Scan. > > I of course did

[GENERAL] Simple Query not using Primary Key Index

Hi, I noticed when I do a simple SELECT id FROM mytable WHERE id = 'cb81d070-4213-465f-b32e-b8db43b83a25'::UUID Postgres does not use the primary key index and opts for a Seq Scan. I of course did VACUUM ANALYZE and I have reset statistics But no sign. Is there any particular thing I should be