Re: [PATCH] Fix wrong argument to SOFT_ERROR_OCCURRED in timestamptz_date

From: Nathan Bossart <nathandbossart(at)gmail(dot)com>
To: Peter Eisentraut <peter(at)eisentraut(dot)org>
Cc: Jianghua Yang <yjhjstz(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org, jian(dot)universality(at)gmail(dot)com, amitlangote09(at)gmail(dot)com
Subject: Re: [PATCH] Fix wrong argument to SOFT_ERROR_OCCURRED in timestamptz_date
Date: 2026-03-25 19:18:00
Message-ID: acQ06D_Lz6V93gDg@nathan
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Mar 25, 2026 at 07:17:15AM +0100, Peter Eisentraut wrote:
> On 24.03.26 21:53, Nathan Bossart wrote:
>> LGTM. To prevent this from happening in the future, I think we ought to
>> change SOFT_ERROR_OCCURRED to a static inline function. I tried that, and
>> I got the following warnings:
>>
>> execExprInterp.c:4964:27: warning: incompatible pointer types passing 'ErrorSaveContext *' (aka 'struct ErrorSaveContext *') to parameter of type 'Node *' (aka 'struct Node *') [-Wincompatible-pointer-types]
>> 4964 | if (SOFT_ERROR_OCCURRED(&jsestate->escontext))
>> | ^~~~~~~~~~~~~~~~~~~~
>> ../../../src/include/nodes/miscnodes.h:54:27: note: passing argument to parameter 'escontext' here
>> 54 | SOFT_ERROR_OCCURRED(Node *escontext)
>> | ^
>> execExprInterp.c:5200:26: warning: incompatible pointer types passing 'ErrorSaveContext *' (aka 'struct ErrorSaveContext *') to parameter of type 'Node *' (aka 'struct Node *') [-Wincompatible-pointer-types]
>> 5200 | if (SOFT_ERROR_OCCURRED(&jsestate->escontext))
>> | ^~~~~~~~~~~~~~~~~~~~
>> ../../../src/include/nodes/miscnodes.h:54:27: note: passing argument to parameter 'escontext' here
>> 54 | SOFT_ERROR_OCCURRED(Node *escontext)
>> | ^
>>
>> I think we just need to add casts to "Node *" for those. AFAICT there
>> isn't an actual bug.
>
> Or maybe we change the escontext field to be of type Node *?

I started looking at this, but it seems to be a rather invasive change for
the level of gain. Not only does it require more memory management, but we
then have to cast it many places like this:

((ErrorSaveContext *) jsestate->escontext)->error_occured = false;

If we instead make it an ErrorSaveContext *, we'd still need to cast it to
Node * for SOFT_ERROR_OCCURRED, unless we had it accept a void * or
something, which defeats the purpose.

--
nathan

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Roberto Mello 2026-03-25 19:50:45 pg_publication_tables: return NULL attnames when no column list is specified
Previous Message Bharath Rupireddy 2026-03-25 19:17:17 Re: Introduce XID age based replication slot invalidation