Re: pgsql: Improve index AMs' opclass validation procedures.

From: David Rowley <david(dot)rowley(at)2ndquadrant(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-committers(at)postgresql(dot)org
Subject: Re: pgsql: Improve index AMs' opclass validation procedures.
Date: 2016-01-22 01:48:20
Message-ID: CAKJS1f828VX=FzMOmAKBqNVh9D3KH_OVQdzqbv0H9uFGZ1G23A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

On 22 January 2016 at 13:47, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Improve index AMs' opclass validation procedures.
>
> The amvalidate functions added in commit 65c5fcd353a859da were on the
> crude side. Improve them in a few ways:
>
> * Perform signature checking for operators and support functions.
>
> * Apply more thorough checks for missing operators and functions,
> where possible.
>
> * Instead of reporting problems as ERRORs, report most problems as INFO
> messages and make the amvalidate function return FALSE. This allows
> more than one problem to be discovered per run.
>
> * Report object names rather than OIDs, and work a bit harder on making
> the messages understandable.
>
> Also, remove a few more opr_sanity regression test queries that are
> now superseded by the amvalidate checks.

I'm getting 3 new warnings with this change which mention about 32-bit
bit shifting then bitwise anding to a 64-bit variable.

The attached fixes the warnings

--
David Rowley http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

Attachment Content-Type Size
amvalidate_64bit_bitshift.patch application/octet-stream 1.7 KB

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2016-01-22 02:14:13 pgsql: Suppress compiler warning.
Previous Message Tom Lane 2016-01-22 00:47:25 pgsql: Improve index AMs' opclass validation procedures.