Re: pgsql: Add pg_plan_advice contrib module.

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: David Rowley <dgrowleyml(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: pgsql: Add pg_plan_advice contrib module.
Date: 2026-03-17 13:59:10
Message-ID: CA+TgmoZw5tx_Jyxr-KeNAXsPV1yQ4ducgieUxY6+ghd33tCn9Q@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

On Mon, Mar 16, 2026 at 5:12 PM David Rowley <dgrowleyml(at)gmail(dot)com> wrote:
> I was just building with VS2026 when I noticed the following warning:
>
> ../contrib/pg_plan_advice/pgpa_planner.c(1195): warning C4319: '~':
> zero extending 'uint32' to 'uint64' of greater size
>
> I guess the compiler is concerned that you might not have meant to
> unconditionally switch off all the upper 32-bits of the 64-bit
> variable. Adding the following does get rid of the warning for me,
> but not sure if that's what you had intended. I've not studied the
> code enough to understand why there are two different integer widths
> being used for the bits.
>
> - *pgs_mask_p &= ~(PGS_JOIN_ANY & ~join_mask);
> + *pgs_mask_p &= (uint32) ~(PGS_JOIN_ANY & ~join_mask);

Thanks for the report. This is an error on my part, pure and simple.
At one point, pgs_mask was a 32-bit value, and although that changed
months ago, this holdover escaped detection. I'll go fix that.

--
Robert Haas
EDB: http://www.enterprisedb.com

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Nathan Bossart 2026-03-17 14:26:55 pgsql: Add more columns to pg_stats, pg_stats_ext, and pg_stats_ext_exp
Previous Message Peter Eisentraut 2026-03-17 13:14:48 pgsql: Dump labels in reproducible order

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrei Lepikhov 2026-03-17 14:05:08 Re: Read-only connection mode for AI workflows.
Previous Message Peter Eisentraut 2026-03-17 13:57:39 Re: SQL Property Graph Queries (SQL/PGQ)