Hi~ hackers Back to v17, commit 21d9c3ee gave SMgrRelation a well-defined lifetime, and smgrclose nolonger removes SMgrRelation object from the hashtable, leaving the work to smgrdestroyall. But I find a place that relies on the removing behavior previously, but is still calling smgrclose.
Startup process of standby will redo table dropping with DropRelationFiles, using smgrdounlinkall to drop buffers and unlink physical files, and then uses smgrclose to destroy the SMgrRelation object. I think it should use smgrdestroy here, or the object memory will be leaked. With concurrent clients, the following pgbench script will produce the memory leak of a standby startup process easily. Entries will be entered into the hashtable but never removed. pgbench -f bench.sql -n -c 32 -j 32 -T 600 ```sql DROP TABLE IF EXISTS tbl:client_id; CREATE TABLE tbl:client_id (id int); ``` The attached patch export smgrdestroy as a public function, and use it in DropRelationFiles. — Regards, Jingtang
v1-0001-Fix-SMgrRelation-object-memory-leak-in-DropRelationF.patch
Description: Binary data
