From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | David Fetter <david(at)fetter(dot)org> |
Cc: | Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Jeremy Drake <pgsql(at)jdrake(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net>, PostgreSQL Patches <pgsql-patches(at)postgresql(dot)org>, Neil Conway <neilc(at)samurai(dot)com> |
Subject: | Re: patch adding new regexp functions |
Date: | 2007-02-16 00:35:46 |
Message-ID: | 5214.1171586146@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
David Fetter <david(at)fetter(dot)org> writes:
> I've obviously misunderstood the scope of the TODO because it appears
> that an INSERT into pg_type at creation time for compound types that
> looks something like the below would do it. What have I missed?
There are a couple of issues. One is that we probably don't want two
pg_type entries for every single table. Will you be satisfied if only
CREATE TYPE AS ... makes an array type? The other is that, at least at
the time they were written, the array support routines couldn't handle
composite array values. Things might or might not be easier today;
I don't think we had record_in and record_out in their current form
then.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2007-02-16 00:50:26 | Re: WIP patch - INSERT-able log statements |
Previous Message | Tom Dunstan | 2007-02-15 23:58:18 | Re: "anyelement2" pseudotype |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2007-02-16 00:50:26 | Re: WIP patch - INSERT-able log statements |
Previous Message | Alvaro Herrera | 2007-02-16 00:07:18 | remove dbname arg from bootstrap mode |