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

Saving a card with related resource nodes either times out or takes much longer than cards w/o those node data types. #9746

Closed
apeters opened this issue Jul 7, 2023 · 1 comment
Assignees
Labels
Type: Bug Something isn't working

Comments

@apeters
Copy link
Member

apeters commented Jul 7, 2023

If a card is saved that has a related resource node and that node is populated, then the save operation can be orders of magnitude slower. On very large datasets (100M tiles, 13M resource instances) this operation can time out.

If you have a card w/o a related resource node, or the card does have a related resource node, but you don't save a value to that node then the save operation is similar to saves of other cards with other datatypes.

@apeters apeters added the Type: Bug Something isn't working label Jul 7, 2023
@apeters apeters self-assigned this Jul 7, 2023
@chiatt chiatt added this to pipeline Jul 7, 2023
apeters added a commit that referenced this issue Jul 8, 2023
@apeters
Copy link
Member Author

apeters commented Jul 8, 2023

link to original and optimized analyzed execution plans:
https://explain.depesz.com/s/Zsneq

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Bug Something isn't working
Projects
Archived in project
Development

No branches or pull requests

2 participants