Re: Misleading comment in tuplesort_set_bound

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
Cc: James Coleman <jtc331(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Misleading comment in tuplesort_set_bound
Date: 2019-09-12 14:00:31
Message-ID: 14435.1568296831@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> writes:
> [ shrug ] It seemed to require no further work, so I just pushed Tom's
> proposed change.
> I added an empty line after the new combined assertion, which makes
> clearer (to me anyway) that the other assertions are unrelated.

Actually, the thing I wanted to add was some actual comments for
those other assertions. But that requires a bit of research that
I hadn't made time for...

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2019-09-12 14:11:53 Re: Runtime pruning problem
Previous Message Alexander Korotkov 2019-09-12 14:00:02 Re: [PATCH] ltree, lquery, and ltxtquery binary protocol support