From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | pgsql-hackers(at)postgreSQL(dot)org |
Subject: | Polymorphic types vs. domains |
Date: | 2008-12-08 01:46:13 |
Message-ID: | 4887.1228700773@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
The proximate cause of this complaint:
http://archives.postgresql.org/pgsql-general/2008-12/msg00283.php
seems to be that the polymorphic-type code doesn't consider a domain
over an enum type to match an ANYENUM function argument.
ISTM this is probably wrong: we need such a domain to act like its base
type for matching purposes. There is an analogous problem with a domain
over an array type failing to match ANYARRAY; conversely, such a domain
is considered to match ANYNONARRAY which it likely should not.
Comments? If this is agreed to be a bug, should we consider
back-patching it? (I'd vote not, I think, because the behavioral
change could conceivably break some apps that work now.)
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2008-12-08 01:54:19 | Re: Updates of SE-PostgreSQL 8.4devel patches (r1268) |
Previous Message | KaiGai Kohei | 2008-12-08 01:37:09 | Re: Updates of SE-PostgreSQL 8.4devel patches (r1268) |