Re: plperl features

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: Sergej Sergeev <sergej(at)commandprompt(dot)com>, pgsql-patches <pgsql-patches(at)postgresql(dot)org>
Subject: Re: plperl features
Date: 2005-06-10 03:40:25
Message-ID: 17559.1118374825@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-patches

Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)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

In response to

Responses

Browse pgsql-patches by date

  From Date Subject
Next Message Tom Lane 2005-06-10 03:47:18 Re: final light versions of Oracle compatibility (SQLSTATE, GREATEST,
Previous Message Bruce Momjian 2005-06-10 03:02:36 Re: [HACKERS] PGPASSWORD and client tools