>>>>> "Tom" == Tom Lane <t...@sss.pgh.pa.us> writes:
[domain -> base type conversion interfering with optimization] Tom> You seem to be laboring under the delusion that this is Tom> considered a bug. Of course it's a bug, or at least a missing feature - there is no justification for putting performance deathtraps in the way of using domains. Tom> It's a necessary semantic restriction, because the pushed-down Tom> expression could mean different things when applied to different Tom> data types. How? Type-dependent selection of operators has already been done as part of parse analysis, no? And the domain -> base conversion is purely a relabelling, no? So what semantic change is possible as a result? -- Andrew (irc:RhodiumToad) -- Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance
