sequential scan when using bigint value - Mailing list pgsql-general

From David Garamond
Subject sequential scan when using bigint value
Date
Msg-id 405AF3C8.1030601@zara.6.isreserved.com
Whole thread Raw
Responses Re: sequential scan when using bigint value
Re: sequential scan when using bigint value
List pgsql-general
I have a table of 2mil records. The table consists of two columns, id
(BYTEA/GUID, PK) and i (INT, UNIQUE INDEX). Could someone explain why,
when using a bigint value like this:

  select * from partition where i=3000000000;

or

  select * from partition where i in (1,2,3,3000000000);

Postgres immediately switches from index scan to seq scan?

--
dave

pgsql-general by date:

Previous
From: "Bas Scheffers"
Date:
Subject: Re: "People near me" query
Next
From: BRINER Cedric
Date:
Subject: self referenced table ?