Horton

Re: Misleading comment in tuplesort_set_bound

Alvaro Herrera <alvherre@2ndquadrant.com>

View thread View on postgr.es
From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: James Coleman <jtc331@gmail.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2019-09-12T13:39:34Z
Lists: pgsql-hackers 
On 2019-Sep-05, James Coleman wrote:

> Yes, planning on it, just a bit behind right now so will likely be a
> few more days at least.

[ 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.

Thanks

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

Commits

  1. Make tuplesort_set_bound() assertions more comprehensible, hopefully.

  2. Merge two assertions to make comment clearer