Skip to content

fix(backend): various database session fixes #6309

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

Draft
wants to merge 3 commits into
base: stable
Choose a base branch
from

Conversation

fatih-acar
Copy link
Contributor

No description provided.

@github-actions github-actions bot added the group/backend Issue related to the backend (API Server, Git Agent) label Apr 15, 2025
Copy link

codspeed-hq bot commented Apr 15, 2025

CodSpeed Performance Report

Merging #6309 will not alter performance

Comparing fac-fix-db-sessions (dab8694) with stable (6d381f6)

Summary

✅ 10 untouched benchmarks

await relationship_manager.fetch_relationship_ids(db=db, force_refresh=True)
for relationship_constraint in self.relationship_manager_constraints:
await relationship_constraint.check(relm=relationship_manager, node_schema=node.get_schema())
if not self.db.is_transaction:
Copy link
Collaborator

Choose a reason for hiding this comment

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

We need to be careful here, as far as I remember one of the reason we are starting a new session is that otherwise we can't use the parallel runtime to check the uniqueness constraint and it will impact performance
I could be wrong here, I need to look deeper in the code

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
group/backend Issue related to the backend (API Server, Git Agent)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants