Re: Improper use about DatumGetInt32 - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: Improper use about DatumGetInt32
Date
Msg-id 09e2dd82-4eb6-bba1-271a-d2b58bf6c71f@enterprisedb.com
Whole thread Raw
In response to Re: Improper use about DatumGetInt32  (Michael Paquier <michael@paquier.xyz>)
Responses Re: Improper use about DatumGetInt32  (Michael Paquier <michael@paquier.xyz>)
List pgsql-hackers
On 2021-01-11 09:09, Michael Paquier wrote:
> On Sat, Jan 09, 2021 at 01:41:39PM +0100, Peter Eisentraut wrote:
>> If we had a way to do such testing then we wouldn't need these markers. But
>> AFAICT, we don't.
> 
> Not sure I am following your point here.  Taking your patch, it is
> possible to trigger the version of get_raw_page() <= 1.8 just with
> something like the following:
> create extension pageinspect version "1.8";
> select get_raw_page('pg_class', 0);
> 
> There are no in-core regression tests that check the compatibility of
> extensions with older versions, but it is technically possible to do
> so.

Interesting idea.  Here is a patch that incorporates that.

Attachment

pgsql-hackers by date:

Previous
From: Kyotaro Horiguchi
Date:
Subject: Re: Disable WAL logging to speed up data loading
Next
From: Ajin Cherian
Date:
Subject: Re: Track replica origin progress for Rollback Prepared