| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
| Cc: | Andreas Seltenreich <seltenreich(at)gmx(dot)de>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [sqlsmith] Failed assertion in _hash_splitbucket_guts |
| Date: | 2016-12-05 16:51:13 |
| Message-ID: | CA+TgmoZea8NxEVu9B0Y=-88UjtzEVX77PEtc_=Lze2NVd591-A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Dec 2, 2016 at 10:04 PM, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> wrote:
>> Here we shouldn't be accessing meta page after releasing the lock as
>> concurrent activity can change these values. This can be fixed by
>> storing these values in local variables before releasing the lock and
>> passing local variables in hashbucketcleanup(). I will send patch
>> shortly.
>
> Please find attached patch to fix above code.
Committed. I don't know either whether this will fix things for
Andreas, but it's certainly a bug fix in its own right.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2016-12-05 16:52:57 | Re: Tackling JsonPath support |
| Previous Message | Masahiko Sawada | 2016-12-05 16:49:16 | Re: The max value of autovacuum_vacuum/analyze_scale_factor. |