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

Responses

• Re: Polymorphic types vs. domains at 2008-12-08 08:00:49 from David E. Wheeler
• Re: Polymorphic types vs. domains at 2009-01-20 17:08:55 from Bruce Momjian
• Re: Polymorphic types vs. domains at 2009-02-04 19:29:29 from Bruce Momjian

pgsql-hackers by date

Next:	From: Bruce Momjian	Date: 2008-12-08 01:54:19
	Subject: Re: Updates of SE-PostgreSQL 8.4devel patches (r1268)
Previous:	From: KaiGai Kohei	Date: 2008-12-08 01:37:09
	Subject: Re: Updates of SE-PostgreSQL 8.4devel patches (r1268)