From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Ashutosh Sharma <ashu(dot)coek88(at)gmail(dot)com> |
Cc: | Kuntal Ghosh <kuntalghosh(dot)2007(at)gmail(dot)com>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: WAL Consistency checking for hash indexes |
Date: | 2017-03-14 19:02:04 |
Message-ID: | CA+TgmoYHbOXG1gmAGs6sY91YsdF_t9Ai2kXHZF=XcYK9zOqDNg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Mar 13, 2017 at 10:36 AM, Ashutosh Sharma <ashu(dot)coek88(at)gmail(dot)com> wrote:
> Couple of review comments,,
>
> You may also need to update the documentation as now we are also going
> to support wal consistency check for hash index. The current
> documentation does not include hash index.
>
> + only records originating from those resource managers. Currently,
> + the supported resource managers are <literal>heap</>,
> + <literal>heap2</>, <literal>btree</>, <literal>gin</>,
> + <literal>gist</>, <literal>sequence</>, <literal>spgist</>,
> + <literal>brin</>, and <literal>generic</>. Only
Did that, committed this. Also ran pgindent over hash_mask() and
fixed an instance of dubious capitalization.
> Following comment in hash_mask() may require changes if patch for
> 'Microvacuum support for Hash Index - [1]' gets committed.
>
> + /*
> + * In hash bucket and overflow pages, it is possible to modify the
> + * LP_FLAGS without emitting any WAL record. Hence, mask the line
> + * pointer flags.
> + * See hashgettuple() for details.
> + */
If that's so, then that patch is responsible for updating these
comments (and the code, if necessary).
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Jeff Janes | 2017-03-14 19:02:48 | Re: Authentication tests, and plain 'password' authentication with a SCRAM verifier |
Previous Message | Stephen Frost | 2017-03-14 18:56:26 | Re: Write Ahead Logging for Hash Indexes |