| From: | Kevin Grittner <kgrittn(at)ymail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Kouhei Kaigai <kaigai(at)ak(dot)jp(dot)nec(dot)com>, David Rowley <david(dot)rowley(at)2ndquadrant(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Bug? ExecChooseHashTableSize() got assertion failed with crazy number of rows |
| Date: | 2015-08-19 15:15:47 |
| Message-ID: | 1227259396.4292542.1439997347927.JavaMail.yahoo@mail.yahoo.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> I'm still doubtful that this is the only overflow risk in that
> new ExecChooseHashTableSize code, though.
KaiGai already pointed that out on this thread and I completely
agree; but I figured that I might as well fix the clear bug with an
obvious fix that was causing an assertion failure during 9.5
testing pending analysis and fixes for the other hazards. Getting
past the assertion failure might help identify some other bugs in
the area.
--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tatsuo Ishii | 2015-08-19 15:17:35 | Re: Proposal: Implement failover on libpq connect level. |
| Previous Message | Tom Lane | 2015-08-19 15:06:59 | Re: Bug? ExecChooseHashTableSize() got assertion failed with crazy number of rows |