From: Balazs Nagy <bnagy@thenewpush.com>
To: pgsql-bugs@postgresql.org
Subject: BUG #2737: hash indexing large table fails, while btree of same index works
Date: Sun, 5 Nov 2006 13:47:31 GMT
Message-ID: <200611051347.kA5DlVCk032222@wwwmaster.postgresql.org> (raw)
The following bug has been logged online:
Bug reference: 2737
Logged by: Balazs Nagy
Email address: bnagy@thenewpush.com
PostgreSQL version: 8.1.5
Operating system: RHEL4
Description: hash indexing large table fails, while btree of same
index works
Details:
Postgres: 8.1.5
Database table size: ~60 million rows
Field to index: varchar 127
CREATE INDEX ... USING hash ...
fails with a file not found error (psql in verbose mode):
ERROR: 58P01: could not open segment 3 of relation 1663/16439/16509 (target
block 528283): No such file or directory
LOCATION: _mdfd_getseg, md.c:954
VACUUM, VACUUM FULL doesn't help, full dump and reload doesn't help either
CREATE INDEX ... USING btree ...
works fine. Could there be a bug in the hash algorithm's implementation?
System is x86_64 SMP 8 CPU core, 16GB RAM, Fiber channel SAN, kernel
2.6.9-42.0.3.ELsmp
I haven't tried the 8.2beta2 yet, but would be happy to try, as the hash
method is better suited for the kind of index I need...
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: bnagy@thenewpush.com, pgsql-bugs@postgresql.org
Subject: Re: BUG #2737: hash indexing large table fails, while btree of same index works
In-Reply-To: <200611051347.kA5DlVCk032222@wwwmaster.postgresql.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox