Stu Coates (stu@stucoates.com) reports a bug with a severity of 2
The lower the number the more severe it is.
Short Description
Not performing index scan for 64bit primary
Long Description
When performing a query against a table that has a 64bit (int8) primary key a sequential scan always takes place.
Changingthe key to a 32bit (int4) one will result in the _pkey index being used (after a vacuum -analyze is ran). This
resultsin a huge performance hit when using 64bit foreign keys and referential integrity checks when the data volumes
arelarge (>1M rows).
PostgreSQL version: 7.0.2 on powerpc-unknown-linux-gnu, compiled by gcc 2.95.2
Sample Code
Example code at: http://www.filesys.demon.co.uk/postgresBug.html
No file was uploaded with this report
