| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | pgsql-committers(at)postgresql(dot)org |
| Subject: | pgsql: Clarify type resolution behavior for domain types. |
| Date: | 2014-08-10 20:13:57 |
| Message-ID: | E1XGZV7-00070g-Tv@gemulon.postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
Clarify type resolution behavior for domain types.
The user documentation was vague and not entirely accurate about how
we treat domain inputs for ambiguous operators/functions. Clarify
that, and add an example and some commentary. Per a recent question
from Adam Mackler.
It's acted like this ever since we added domains, so back-patch
to all supported branches.
Branch
------
REL9_3_STABLE
Details
-------
http://git.postgresql.org/pg/commitdiff/d4b13fab4e009c52567283b4b42b190c4696c355
Modified Files
--------------
doc/src/sgml/typeconv.sgml | 102 ++++++++++++++++++++++++++++++++++++++------
1 file changed, 89 insertions(+), 13 deletions(-)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2014-08-10 21:34:27 | Re: pgsql: docs: Improve documentation of \pset without arguments. |
| Previous Message | Fujii Masao | 2014-08-10 16:55:59 | Re: pgsql: docs: Improve documentation of \pset without arguments. |