Postgres Pro
Downloads
Home   >   mailing lists

Re: preferred way to use PG_GETARG_BYTEA_P in SPI - Mailing list pgsql-general

From Tom Lane
Subject Re: preferred way to use PG_GETARG_BYTEA_P in SPI
Date
Msg-id 25355.1192054612@sss.pgh.pa.us
Whole thread Raw
In response to preferred way to use PG_GETARG_BYTEA_P in SPI  ("Merlin Moncure" <mmoncure@gmail.com>)
Responses Re: preferred way to use PG_GETARG_BYTEA_P in SPI  ("Merlin Moncure" <mmoncure@gmail.com>)
List pgsql-general
Tree view 
"Merlin Moncure" <mmoncure@gmail.com> writes:
> I'm curious what's considered the best way to invoke PG_GETARG_BYTEA_P
> in an SPI routine and properly check for null input in non 'strict'
> routines.  Right now, I'm looking at PG_GETARG_POINTER to check for
> null value before using PG_GETARG_BYTEA_P to assign to the bytea
> pointer.

That would be entirely wrong.  In a non-strict function, test
PG_ARGISNULL(n) before attempting any variant of PG_GETARG(n).
Grepping for PG_ARGISNULL will yield lots of examples.

            regards, tom lane

pgsql-general by date:

Previous
From: Ralph Smith
Date:
Subject: Default Ubuntu post-install Qs (PG v7.4)
Next
From: Randall Lucas
Date:
Subject: Coercing compound types to use generic ROW comparison operators