Thread

1. strict-aliasing warning

   ma lz <ma100@hotmail.com> — 2025-12-10T02:27:25Z

   In function "ExecEvalJsonCoercionFinish()"
   
        if (SOFT_ERROR_OCCURRED(&jsestate->escontext))
   
   may produce strict-aliasing warning
   
   Don't use IsA may fix this problem
   

2. Re: strict-aliasing warning

   Adrian Klaver <adrian.klaver@aklaver.com> — 2025-12-10T03:04:23Z

   On 12/9/25 18:27, ma lz wrote:
   
   What version of Postgres?
   
   > In function "ExecEvalJsonCoercionFinish()"
   > 
   >       if (SOFT_ERROR_OCCURRED(&jsestate->escontext))
   > 
   > may produce strict-aliasing warning
   
   > Don't use IsA may fix this problem
   
   Why is it a problem?
   
   This is something that should be submitted here(you will need create a 
   community account):
   
   https://www.postgresql.org/account/login/?next=/account/submitbug/
   
   -- 
   Adrian Klaver
   adrian.klaver@aklaver.com
   
   
   
   

3. Re: strict-aliasing warning

   Michael Paquier <michael@paquier.xyz> — 2025-12-10T06:44:29Z

   On Tue, Dec 09, 2025 at 07:04:23PM -0800, Adrian Klaver wrote:
   > On 12/9/25 18:27, ma lz wrote:
   >> Don't use IsA may fix this problem
   > 
   > Why is it a problem?
   
   Well, I don't think that this has proved to be a problem until now in
   the buildfarm.  I doubt that it would be the only problematic area if
   a new compiler flag is enforced by a buildfarm member, assuming that
   we would add one but the bar is very high when it comes to that.
   
   A 4-line message is short to present your arguments, what you are
   trying to do, and why it could make sense in some way.
   --
   Michael