vsbace opened a new issue, #1850:
URL: https://github.com/apache/cloudberry/issues/1850

   ### Apache Cloudberry version
   
   We are trying to test Apache Cloudberry 2.1.0 on Astra Linux 1.8.1 (Debian 
12 based)
   
   
   ### What happened
   
   Hello,
   We found the next problem with auvacuum worker using not correct logic and 
trying to vacuum PXF foreghn tables located on Hadoop.
   It is caused to high CPU usage by autovacuum workers on database with high 
coung of PXF tables
   
   <img width="1566" height="921" alt="Image" 
src="https://github.com/user-attachments/assets/5a2c6e32-3ef2-406a-b7f8-6bb4f14b9073";
 />
   
   In Cloudberry master log we can see many messages by the next screenshoot we 
can see
   
   <img width="1541" height="884" alt="Image" 
src="https://github.com/user-attachments/assets/f9aa4c81-0f51-48e6-951c-7790610770ed";
 />
   
   When we can run vacuum on problem database, vacuum crashed by the next error
   
   <img width="1152" height="205" alt="Image" 
src="https://github.com/user-attachments/assets/b7b80483-33b4-446f-9a1b-1eb319b1d554";
 />
   
   And we can identify this object as PXF foreighn table
   
   <img width="1360" height="394" alt="Image" 
src="https://github.com/user-attachments/assets/d6c9ee3e-f6a5-493b-8bd8-875aafc10a69";
 />
   
   
   
   
   ### What you think should happen instead
   
   And i think correct about vacuum logic can not work with foreighn tables and 
in Greenplum logic means not use PXF tables too in this mechanizm.
   
   ### How to reproduce
   
   I think need to create couple of PXF tables on clean DB.
   
   ### Operating System
   
   Astra Linux 1.8.1 (Debian 12 based)
   
   ### Anything else
   
   Every time.
   
   ### Are you willing to submit PR?
   
   - [ ] Yes, I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [x] I agree to follow this project's [Code of 
Conduct](https://github.com/apache/cloudberry/blob/main/CODE_OF_CONDUCT.md).
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to