Re: inheritance, and plans - Mailing list pgsql-performance

From Andrew Gierth
Subject Re: inheritance, and plans
Date
Msg-id 87eiyaqgbj.fsf@news-spur.riddles.org.uk
Whole thread Raw
In response to Re: inheritance, and plans  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: inheritance, and plans  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-performance
>>>>> "Tom" == Tom Lane <tgl@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)


pgsql-performance by date:

Previous
From: Grzegorz Jaśkiewicz
Date:
Subject: Re: inheritance, and plans
Next
From: Tom Lane
Date:
Subject: Re: inheritance, and plans