Re: Re: BUG #15039: some question about hash index code
Amit Kapila <amit.kapila16@gmail.com>
From: Amit Kapila <amit.kapila16@gmail.com>
To: Robert Haas <robertmhaas@gmail.com>
Cc: 自己 <zoulx1982@163.com>, pgsql-bugs@lists.postgresql.org, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2018-02-02T02:46:52Z
Lists: pgsql-bugs, pgsql-hackers
On Fri, Feb 2, 2018 at 2:03 AM, Robert Haas <robertmhaas@gmail.com> wrote: > On Thu, Feb 1, 2018 at 1:51 AM, Amit Kapila <amit.kapila16@gmail.com> wrote: >> Attached patch fix_markbufdirty_hash_index_v1.patch fixes the problem >> by calling MarkBufferDirty at the appropriate place in the code. >> However, I noticed that we might end up calling MarkBufferDirty twice >> for metapage in _hash_addovflpage. I think we can easily avoid that >> as is done in patch fix_markbufdirty_hash_index_v1.1.patch. > > IIUC, the v1 patch is fixing a bug, but the v1.1 patch is a minor > optimization. > Yes. > I'm going to take the easy way out and push v1 to v10 > and master. > Okay. -- With Regards, Amit Kapila. EnterpriseDB: http://www.enterprisedb.com
Commits
-
Fix possible failure to mark hash metapage dirty.
- b94988fad561 10.2 landed
- ad25a6b1f25b 11.0 landed