Re: [HACKERS] Hashjoin status report

From: Michael Contzen <mcontzen(at)dohle(dot)com>
To: <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [HACKERS] Hashjoin status report
Date: 1999-05-07 10:11:30
Message-ID: 01be9871$fa35aa60$4dbe7fc2@wcontzen.dohle.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hello,

(using snapshot of May, 5th)

because we have the need to have a workaround to this hash problem, I looked into the hashing code (well, without having the background).

For reducing the probability of an overflow I increased
#define FUDGE_FAC 3
witch was originally 1.5. I think it´s a data dependend constant (correct?) and for my data it works...

It does the job, but certainly that this is not the solution.

Increasing -B 256 doesn´t work:
NOTICE: Buffer Leak: [248] (freeNext=0, freePrev=0, relname=, blockNum=0, flags=0x0, refcount=0 25453)
pq_flush: send() failed, errno 88
pq_recvbuf: recv() failed, errno=88

Kind regards,

Michael Contzen
mcontzen(at)dohle(dot)com
Dohle Systemberatung, Germany

Kind regards,

Michael Contzen
mcontzen(at)dohle(dot)com
Dohle Systemberatung, Germany

Browse pgsql-hackers by date

  From Date Subject
Next Message Tim Perdue 1999-05-07 11:16:25 Weird Errors in 6.4.2 - Indexes/Vacuuming
Previous Message ZEUGSWETTER Andreas IZ5 1999-05-07 08:43:26 AW: [HACKERS] cvs 6.5 regression tests on Linux x86