Re: Do we really want to migrate plproxy and citext into PG core distribution?

From: Zdenek Kotala <Zdenek(dot)Kotala(at)Sun(dot)COM>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "David E(dot) Wheeler" <david(at)kineticode(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org, Andrew Dunstan <andrew(at)dunslane(dot)net>
Subject: Re: Do we really want to migrate plproxy and citext into PG core distribution?
Date: 2008-07-29 19:12:45
Message-ID: 488F6BAD.2000708@sun.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane napsal(a):

>
> Obviously the solution should involve a new column in pg_type and
> a new type property in CREATE TYPE, but what should the representation
> be? A full-on approach would make the type categories be real SQL
> objects with their own system catalog and reference them by OID,
> but I can't help thinking that that's overkill.
>
> Anyway, debating that is probably material for a separate thread ...

The collation support also needs to determine which data type is text/string.

Zdenek

--
Zdenek Kotala Sun Microsystems
Prague, Czech Republic http://sun.com/postgresql

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2008-07-29 19:15:08 Re: TABLE-function patch vs plpgsql
Previous Message David E. Wheeler 2008-07-29 18:53:57 Type Categories for User-Defined Types