Hi,
On 2019-11-04 11:30:23 +, Dagfinn Ilmari Mannsåker wrote:
> Tom Lane writes:
>
> > ilm...@ilmari.org (Dagfinn Ilmari =?utf-8?Q?Manns=C3=A5ker?=) writes:
> >> I just noticed that when contrib/seg was converted to V1 calling
> >> convention (commit 389bb2818f4), the PG_GETARG_SEG_P() macro
Tom Lane writes:
> ilm...@ilmari.org (Dagfinn Ilmari =?utf-8?Q?Manns=C3=A5ker?=) writes:
>> I just noticed that when contrib/seg was converted to V1 calling
>> convention (commit 389bb2818f4), the PG_GETARG_SEG_P() macro got defined
>> in terms of PG_GETARG_POINTER(). But it itself calls DatumGe
ilm...@ilmari.org (Dagfinn Ilmari =?utf-8?Q?Manns=C3=A5ker?=) writes:
> I just noticed that when contrib/seg was converted to V1 calling
> convention (commit 389bb2818f4), the PG_GETARG_SEG_P() macro got defined
> in terms of PG_GETARG_POINTER(). But it itself calls DatumGetPointer(),
> so shouldn
=?UTF-8?q?Dagfinn=20Ilmari=20Manns=C3=A5ker?=
Date: Sat, 2 Nov 2019 22:46:23 +0000
Subject: [PATCH] contrib/seg: Fix PG_GETARG_SEG_P definition
DatumGetPointer() needs a Datum argument, not a pointer.
---
contrib/seg/seg.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/contrib/seg/s
