Re: plperl features - Mailing list pgsql-patches

From Tom Lane
Subject Re: plperl features
Date
Msg-id 17559.1118374825@sss.pgh.pa.us
Whole thread Raw
In response to Re: plperl features  (Bruce Momjian <pgman@candle.pha.pa.us>)
Responses Re: plperl features  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-patches
Bruce Momjian <pgman@candle.pha.pa.us> writes:
> Also, I don't think the arg_is_p variable is really the proper fix for
> this, but I am unsure what to recomment.  Others?

The thing I didn't like about that was that it assumes there is only
one pseudotype behavior that is or ever will be interesting for plperl.

I think it'd probably make more sense to store an array of the parameter
type OIDs and then check for ANYELEMENT or ANYARRAY as such in the
places where the patch uses arg_is_p.

            regards, tom lane

pgsql-patches by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: [HACKERS] PGPASSWORD and client tools
Next
From: Tom Lane
Date:
Subject: Re: final light versions of Oracle compatibility (SQLSTATE, GREATEST,