The proximate cause of this complaint:
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
pgsql-hackers by date
|Next:||From: Bruce Momjian||Date: 2008-12-08 01:54:19|
|Subject: Re: Updates of SE-PostgreSQL 8.4devel patches
|Previous:||From: KaiGai Kohei||Date: 2008-12-08 01:37:09|
|Subject: Re: Updates of SE-PostgreSQL 8.4devel patches (r1268)|