Skip to content
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

Use DISTINCT instead of DINSTINCT ON for /v3/service_instances #4210

Conversation

philippthun
Copy link
Member

On large foundations using PostgreSQL DISTINCT ON might lead to wrong query plans making the resulting execution very slow.

  • I have reviewed the contributing guide

  • I have viewed, signed, and submitted the Contributor License Agreement

  • I have made this pull request to the main branch

  • I have run all the unit tests using bundle exec rake

  • I have run CF Acceptance Tests

On large foundations using PostgreSQL DISTINCT ON might lead to wrong
query plans making the resulting execution very slow.
@philippthun philippthun marked this pull request as ready for review February 7, 2025 08:53
Copy link
Contributor

@johha johha left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Alt Text

@philippthun philippthun merged commit 5b1af26 into cloudfoundry:main Feb 7, 2025
8 checks passed
ari-wg-gitbot added a commit to cloudfoundry/capi-release that referenced this pull request Feb 7, 2025
Changes in cloud_controller_ng:

- Use DISTINCT instead of DINSTINCT ON for /v3/service_instances
    PR: cloudfoundry/cloud_controller_ng#4210
    Author: Philipp Thun <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants