Re: Inaccurate description of UNION/CASE/etc type selection

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
Cc: Pg Docs <pgsql-docs(at)lists(dot)postgresql(dot)org>
Subject: Re: Inaccurate description of UNION/CASE/etc type selection
Date: 2020-08-17 15:31:04
Message-ID: 1073004.1597678264@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-docs

"David G. Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> writes:
> More concisely:

> Make the first input type a candidate type. Each subsequent input type is
> compared to the current candidate, with a new candidate being chosen only
> when there exists a non-mutal implicit cast to the new type. If at any
> point a preferred type is made a candidate then it will be chosen.

So this is just a verbatim statement of the algorithm, which is what
I was hoping to avoid :-(. But maybe there's no simpler way.

regards, tom lane

In response to

Responses

Browse pgsql-docs by date

  From Date Subject
Next Message David G. Johnston 2020-08-17 16:07:26 Re: Inaccurate description of UNION/CASE/etc type selection
Previous Message David G. Johnston 2020-08-17 01:06:25 Re: Inaccurate description of UNION/CASE/etc type selection