Description of problem: Current implementation of UUID generation can generate duplicate UUIDs. We used our own UUID generation since in the past we had to support both PG 8.x and PG 9.x Since now we are supporting only PG 9.x, we can go back to use PG native support of UUID generation. Version-Release number of selected component (if applicable): How reproducible: Happens from time to time in Jenkins CI tests, no exact scenario Steps to Reproduce: 1. 2. 3. Actual results: Algorithm may generate duplicate UUIDs Expected results: Algorithm should not generate duplicate UUIDs Additional info:
Using PG native uuid_generate_vX() functions requires installing an extension to PG which can be done only with an admin user on the database. This is relatively complex and can be done only on a local provisioned database. I would suggest instead to improve the randomness of our UUID generation function such that it will not generate duplicate values. Changing the bug subject accordingly
Removing RFE as we have only reimplemented our own uuid_generate_v1() implementation to produce more random values (instead of replacing it with postgresql extension uuid-ossp) and targeting to 4.0.4 to suppress regular duplicate UUID issues seen on db upgrade jobs on Jenkins.
So this looks like CodeChange - if so nothing for QE.
This issue of duplicate UUIDs during db upgrade is visible only on Jenkins, so yeah no need for QA testing, marking as CodeChange.
Closed as a Code change based on comment #4