Problem Right now, PQL only provides access to the regex pattern match operator. As seen in multiple customer cases, and highlighted in CDPE-2927, this operator can lead to significantly slower queries to postgres when compared to the LIKE operator. In an example dataset from a customer system, a query using the regex operator took 7 minutes to complete, but only 2.5 seconds when replaced with LIKE, as the query planner was able to prioritize the correct index. Recommendation Provide a PQL operator that translates into LIKE when building the resulting SQL to provide users the choice. |