You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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."
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.
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
The text was updated successfully, but these errors were encountered: