> On Mar 2, 2021, at 11:34 AM, Joel Jacobson <j...@compiler.org> wrote: > > Yes. It's random, since equality isn't changed, the sort operation cannot > tell the difference, and nor could a user who isn't aware of upper() / > lower() could reveal differences. This sounds unworkable even just in light of the original motivation for this whole thread. If I use your proposed regexp_positions(string text, pattern text, flags text) function to parse a large number of "positions" from a document, store all those positions in a table, and do a join of those positions against something else, it's not going to work. Positions will randomly vanish from the results of that join, which is going to be really surprising. I'm sure there are other examples of Tom's general point about compares-equal-but-not-equal datatypes. — 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
- Re: [PATCH] Support empty rang... Isaac Morland
- Re: [PATCH] Support empty rang... Joel Jacobson
- Re: [PATCH] Support empty ranges with bound... Chapman Flack
- Re: [PATCH] Support empty ranges with ... Mark Dilger