Re: Bug? ExecChooseHashTableSize() got assertion failed with crazy number of rows
| От | Kevin Grittner |
|---|---|
| Тема | Re: Bug? ExecChooseHashTableSize() got assertion failed with crazy number of rows |
| Дата | |
| Msg-id | 1594535175.4597103.1439991651739.JavaMail.yahoo@mail.yahoo.com обсуждение исходный текст |
| Ответ на | Re: Bug? ExecChooseHashTableSize() got assertion failed with crazy number of rows (Kouhei Kaigai <kaigai@ak.jp.nec.com>) |
| Ответы |
Re: Bug? ExecChooseHashTableSize() got assertion failed with crazy number of rows
|
| Список | pgsql-hackers |
Kouhei Kaigai <kaigai@ak.jp.nec.com> wrote: > we may need a couple of overhaul around HashJoin to support large > size of data, not only nbuckets around 0x80000000. Perhaps, but this is a clear bug, introduced to the 9.5 code, with an obvious fix; so I've pushed the change from 1 to 1L on that left shift. There was clearly an attempt in surrounding code to deal with size overruns by using a long, applying a min(), and casting to int; this one statement just missed a trick. If we need to further constrain sizes to keep within allocation limits, that seems like an entirely separate patch. Thanks for finding and analyzing this and providing a patch! -- Kevin Grittner EDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
В списке pgsql-hackers по дате отправления: