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

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
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 19:25:45
Message-ID: CAKFQuwY6VOoXViQL-W=mB4iz=kAFQdpVzbawY94YdU9zmpExfQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-docs

On Mon, Aug 17, 2020 at 10:11 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> "David G. Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> writes:
> > On Mon, Aug 17, 2020 at 8:31 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> >> 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.
>
> > I got nothin'.
>
> Yeah, me either. So here's a proposed patch, fixing a couple other
> things:
>
>
LGTM

David J.

In response to

Responses

Browse pgsql-docs by date

  From Date Subject
Next Message Tom Lane 2020-08-17 19:40:53 Re: Inaccurate description of UNION/CASE/etc type selection
Previous Message Bruce Momjian 2020-08-17 17:47:27 Re: Request for further clarification on synchronous_commit