Tom Lane wrote:
David Fetter <[EMAIL PROTECTED]> 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?
There should be some better way to create the array type for tables than
directly mangling pg_type, though. Maybe a builtin function that took an
oid?
cheers
andrew
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
