From: | Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | The Hermit Hacker <scrappy(at)hub(dot)org>, pgsql-hackers(at)postgreSQL(dot)org |
Subject: | Re: [HACKERS] Hashjoin status report |
Date: | 1999-05-07 03:49:20 |
Message-ID: | 199905070349.XAA09836@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> The Hermit Hacker <scrappy(at)hub(dot)org> writes:
> >> Opinions? Should I plow ahead, or leave this to fix after 6.5 release?
>
> > Estimate of time involved to fix this? vs likelihood of someone
> > triggering the bug in production?
>
> I could probably get the coding done this weekend, unless something else
> comes up to distract me. It's the question of how much testing it'd
> receive before release that worries me...
>
> As for the likelihood, that's hard to say. It's very easy to trigger
> the bug as a test case. (Arrange for a hashjoin where the inner table
> has a lot of identical rows, or at least many sets of more-than-10-
> rows-with-the-same-value-in-the-field-being-hashed-on.) In real life
> you'd like to think that that's pretty improbable.
>
> What started this go-round was Contzen's report of seeing the
> "hash table out of memory. Use -B parameter to increase buffers"
> message in what was evidently a real-life scenario. So it can happen.
> Do you recall having seen many complaints about that error before?
New optimizer does more hashjoins, so we will see it more often.
--
Bruce Momjian | http://www.op.net/~candle
maillist(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
From | Date | Subject | |
---|---|---|---|
Next Message | Chris Bitmead | 1999-05-07 04:54:51 | Re:pg_dump barfs? |
Previous Message | Chris Bitmead | 1999-05-07 03:36:59 | pg_dump problem? |