> On Mar 2, 2021, at 10:08 AM, Joel Jacobson <j...@compiler.org> wrote: > > On Tue, Mar 2, 2021, at 19:01, Mark Dilger wrote: >> The problem is not just with lower() and upper(), but with equality testing >> (mentioned upthread), since code may rely on two different "positions" (your >> word) both being equal, and both sorting the same. > > That's why the patch doesn't change equality. How does that work if I SELECT DISTINCT ON (nr) ... and then take upper(nr). It's just random which values I get? — Mark Dilger EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
- [PATCH] Support empty ranges with bounds information Joel Jacobson
- Re: [PATCH] Support empty ranges with bounds informatio... Tom Lane
- Re: [PATCH] Support empty ranges with bounds inform... Joel Jacobson
- Re: [PATCH] Support empty ranges with bounds in... Mark Dilger
- Re: [PATCH] Support empty ranges with bound... Joel Jacobson
- Re: [PATCH] Support empty ranges with ... Mark Dilger
- Re: [PATCH] Support empty ranges w... Tom Lane
- Re: [PATCH] Support empty rang... Joel Jacobson
- Re: [PATCH] Support empty ranges w... Joel Jacobson
- Re: [PATCH] Support empty rang... Mark Dilger
- Re: [PATCH] Support empty rang... Mark Dilger
- Re: [PATCH] Support empty rang... Joel Jacobson
- Re: [PATCH] Support empty rang... Mark Dilger
- Re: [PATCH] Support empty rang... Joel Jacobson
- Re: [PATCH] Support empty rang... Mark Dilger
- Re: [PATCH] Support empty rang... Joel Jacobson