From: | pgsql-bugs(at)postgresql(dot)org |
---|---|
To: | pgsql-bugs(at)postgresql(dot)org |
Subject: | PostgreSQL BugTool Submission |
Date: | 2000-08-23 21:53:13 |
Message-ID: | 200008232153.e7NLrD061782@hub.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Stu Coates (stu(at)stucoates(dot)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. Changing the key to a 32bit (int4) one will result in the _pkey index being used (after a vacuum -analyze is ran). This results in a huge performance hit when using 64bit foreign keys and referential integrity checks when the data volumes are large (>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
From | Date | Subject | |
---|---|---|---|
Next Message | Stephan Szabo | 2000-08-23 22:01:36 | Re: PostgreSQL BugTool Submission |
Previous Message | pgsql-bugs | 2000-08-23 18:54:42 | PostgreSQL BugTool Submission |