Comment 2 for bug 1820339

Hmm, this solution appears to not be backwards compatible with less than PG 10 (like if someone was running PG 9.4-9.6) because REGEXP_MATCH() only exists in PG10+ according to PG documentation. They included a tip for changing these to some sort of sub-select for REGEXP_MATCHES() - https://www.postgresql.org/docs/current/functions-matching.html

Have to test further, or we need to decide to make a new Evergreen minimum requirement of PG10+ for next release?