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

pgsql_job_cache folder size grows unusually large #7691 #7908

Open
adnanhamdussalam opened this issue Feb 21, 2025 · 2 comments
Open

pgsql_job_cache folder size grows unusually large #7691 #7908

adnanhamdussalam opened this issue Feb 21, 2025 · 2 comments
Labels
bug needs-more-info requires repro steps or version etc.

Comments

@adnanhamdussalam
Copy link

Hi,

I am facing the same issue (pgsql_job_cache folder size grows unusually large #7691) and there are no active queries that executing but still the size is very high of pgsql_job_cache as you mention in the #7691 as a workaround, we can manually remove the folders in directory pgsql_job_cache.

Kindly can you confirm it?

PG Version: 16.3
Citus Version: 12.1.4

@ihalatci
Copy link
Collaborator

Thank you for reporting. I just closed the linked issue due to no activity. Can you please provide further details/reproduction steps that led you to this state. As mentioned in #7691, "... If there is no query running at the moment, it should be fine to empty pgsql_job_cache folder."

@ihalatci ihalatci added bug needs-more-info requires repro steps or version etc. labels Feb 25, 2025
@adnanhamdussalam
Copy link
Author

Thank you for the update. In my database there is a lot of hash joins against huge tables but when query completes, or session ended then this folder "pgsql_job_cache" should empty automatically but it does not release the space at disk, so I do not want to get into a disaster situation after removing the files from the folder. So, I was just want the reconfirmation that it is safe to remove the files without impacting the database if no query is in executing state.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug needs-more-info requires repro steps or version etc.
Projects
None yet
Development

No branches or pull requests

2 participants