From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk> |
Cc: | Grzegorz Jaśkiewicz <gryzman(at)gmail(dot)com>, pgsql-performance(at)postgresql(dot)org |
Subject: | Re: inheritance, and plans |
Date: | 2009-02-08 18:34:05 |
Message-ID: | 23440.1234118045@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk> writes:
> 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?
Domain conversions are *not* simply relabellings. It's possible now to
have domain-specific functions/operators, and the likely future
evolution of the system is to make that work better rather than remove it.
It's possible that there are specific cases where the UNION optimization
checks could allow domains to be treated as their base types, but
blindly smashing both sides of the check to base is going to break more
cases than it fixes.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Gierth | 2009-02-08 18:58:51 | Re: inheritance, and plans |
Previous Message | Andrew Gierth | 2009-02-07 17:58:56 | Re: inheritance, and plans |