Re: Re: BUG #15039: some question about hash index code - Mailing list pgsql-bugs

From Amit Kapila
Subject Re: Re: BUG #15039: some question about hash index code
Date
Msg-id CAA4eK1+WdnOcYAx5RMy0uJ9Y-0A-yzo1hYcs+a4etZc6KhY-9g@mail.gmail.com
Whole thread Raw
In response to Re: Re: BUG #15039: some question about hash index code  (Amit Kapila <amit.kapila16@gmail.com>)
Responses Re: Re: BUG #15039: some question about hash index code  (Robert Haas <robertmhaas@gmail.com>)
Re: Re: BUG #15039: some question about hash index code  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-bugs
On Wed, Jan 31, 2018 at 6:14 PM, Amit Kapila <amit.kapila16@gmail.com> wrote:
> On Wed, Jan 31, 2018 at 5:57 PM, 自己 <zoulx1982@163.com> wrote:
>> thank you for your quick reply.
>> and i have another question, for the following code, whether exist such
>> scene : page_found is false and
>> newmapbuf is invalid, if so, may be the statement MarkBufferDirty(metabuf);
>> should be placed outside the if statement ?
>>
>
> On a quick look, your observation seems to be right and I think in
> this function we might call markbufferdirty twice for meta page which
> doesn't seem to be required.
>

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.

--
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com

Attachment

pgsql-bugs by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: [BUGS] BUG #14898: pg_upgrade documentation is misleading
Next
From: PG Bug reporting form
Date:
Subject: BUG #15042: Parition by list using enums odd behaviour