"Merlin Moncure" <[EMAIL PROTECTED]> 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
---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
