Re: Improper use about DatumGetInt32

From: Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>
To: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
Cc: Ashutosh Bapat <ashutosh(dot)bapat(at)enterprisedb(dot)com>, Ashutosh Bapat <ashutosh(dot)bapat(at)2ndquadrant(dot)com>, Ashutosh Bapat <ashutosh(dot)bapat(dot)oss(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, "Hou, Zhijie" <houzj(dot)fnst(at)cn(dot)fujitsu(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Improper use about DatumGetInt32
Date: 2020-12-03 09:24:03
Message-ID: 859a7b20-9b4c-0add-6704-6fc5ef4ef9e1@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2020-11-30 16:32, Alvaro Herrera wrote:
> On 2020-Nov-30, Peter Eisentraut wrote:
>
>> Patch updated this way. I agree it's better that way.
>
> Thanks, LGTM.

For a change like this, do we need to change the C symbol names, so that
there is no misbehavior if the shared library is not updated at the same
time as the extension is upgraded in SQL?

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Kapila 2020-12-03 09:27:08 Single transaction in the tablesync worker?
Previous Message Bharath Rupireddy 2020-12-03 08:57:22 Re: Multi Inserts in CREATE TABLE AS - revived patch