Re: [PERFORM] [BUGS] BUG #2737: hash indexing large table fails,while btree of same index works

2006-11-16 Thread Tom Lane
"Simon Riggs" <[EMAIL PROTECTED]> writes: > On Fri, 2006-11-10 at 18:55 -0500, Tom Lane wrote: >> One thought that comes to mind is to require hash to do an smgrextend() >> addressing the last block it intends to use whenever it allocates a new >> batch of blocks, whereupon md.c could adopt a saner

Re: [PERFORM] [BUGS] BUG #2737: hash indexing large table fails,while btree of same index works

2006-11-11 Thread Simon Riggs
On Fri, 2006-11-10 at 18:55 -0500, Tom Lane wrote: > [ cc'ing to pgsql-performance because of performance issue for hash indexes ] > > "Balazs Nagy" <[EMAIL PROTECTED]> writes: > > Database table size: ~60 million rows > > Field to index: varchar 127 > > > CREATE INDEX ... USING hash ... I'd be

Re: [BUGS] BUG #2737: hash indexing large table fails, while btree of same index works

2006-11-10 Thread Tom Lane
[ cc'ing to pgsql-performance because of performance issue for hash indexes ] "Balazs Nagy" <[EMAIL PROTECTED]> writes: > 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: 5

[BUGS] BUG #2737: hash indexing large table fails, while btree of same index works

2006-11-05 Thread Balazs Nagy
The following bug has been logged online: Bug reference: 2737 Logged by: Balazs Nagy Email address: [EMAIL PROTECTED] PostgreSQL version: 8.1.5 Operating system: RHEL4 Description:hash indexing large table fails, while btree of same index works Details: Postgres: 8.