Re: "anyelement2" pseudotype

From: Tom Dunstan <tom(at)tomd(dot)cc>
To: Matt Miller <pgsql(at)mattmillersf(dot)fastmail(dot)fm>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: "anyelement2" pseudotype
Date: 2007-02-15 00:10:17
Message-ID: 45D3A4E9.9010206@tomd.cc
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Dunstan wrote:
> Tom Lane wrote:
>> As for actually adding it, grep for all references to ANYELEMENT and add
>> code accordingly; shouldn't be that hard. Note you'd need to add an
>> anyarray2 at the same time for things to keep working sanely.
>
> The enum patch [1] does exactly this with an ANYENUM pseudo-type. It
> should provide a pretty good overview of what will be required.

Whoops. I just had a look at the mail that Matt referenced at the top of
this thread. An anyelement2 would require a bit more than what anyenum
does, as the type-matching code that ensures that all generic args are
of the same type would have to be changed, unlike anyenum. Hope I didn't
lead you down the wrong path, Matt. OTOH, following the enum patch
should land you in roughly the right areas, and you'd still need to add
ANYELEMENT2 references in all the places that I had to add ANYENUM as well.

Cheers

Tom

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Gregory Stark 2007-02-15 00:43:22 Re: Plan for compressed varlena headers
Previous Message Tom Dunstan 2007-02-14 23:26:15 Re: "anyelement2" pseudotype