-
Notifications
You must be signed in to change notification settings - Fork 3.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
sql: st_simplifypreservetopology can be non-deterministic #91800
Comments
This is very strange. I can reproduce as follows on master with
Most of the time, the
But sometimes it returns:
I can reproduce reliably by running the last command over and over again. Usually I see both results with no more than 10 runs in a row. @otan, do you have any theories about why |
(Note that |
this is entirely using a third party library :( looks like this was recently fixed to be deterministic -- libgeos/geos@e1b10c7. we can apply this patch to our version of GEOS if we wanted to. one day we should also consider updating GEOS / PostGIS. |
To fix this, would we need to create a new fork of geos, similar to https://github.com/cockroachdb/geos or would it suffice to sync that fork with the latest code? The latter might impact builds of older CRDB releases. References to the libgeos version would need to be updated from 3.8.1 to 3.12.0 as well.
Maybe SQL Queries shouldn't be making these changes, but another team? |
libgeos is due for an upgrade for sure, i think the master branch has everything we needed since we made the fork. |
@cockroachdb/dev-inf We may need some help upgrading libgeos |
let's see how #106642 goes |
need dev-inf's help upgrading the |
yep |
roachtest.costfuzz failed with artifacts on release-22.2 @ 9ec2ddb8dc118ce91bf806612bc4c0f86dd7b32b:
Parameters:
ROACHTEST_cloud=gce
,ROACHTEST_cpu=4
,ROACHTEST_encrypted=false
,ROACHTEST_ssd=0
Help
See: roachtest README
See: How To Investigate (internal)
Same failure on other branches
This test on roachdash | Improve this report!
Jira issue: CRDB-21436
The text was updated successfully, but these errors were encountered: