Re: Memory leak of SMgrRelation object on standby

From: 邱宇航 <iamqyh(at)gmail(dot)com>
To: Jingtang Zhang <mrdrivingduck(at)gmail(dot)com>
Cc: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Memory leak of SMgrRelation object on standby
Date: 2025-08-25 02:46:43
Message-ID: 4E5282D5-397F-45A7-9C58-7C9C396FE561@gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> 2025年8月21日 23:07，Jingtang Zhang <mrdrivingduck(at)gmail(dot)com> 写道：
>
> Also, in this situation, should startup process be treated as a background
> worker similar to bgwriter/checkpointer and call smgrdestroyall in some
> period?

Agree with that. Maybe we can call smgrdestroyall in startup process when
replaying CHECKPOINT records, just like bgwriter/checkpointer, which free
all smgr objects after any checkpoint.

Best regards,
Yuhang Qiu

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message jian he 2025-08-25 02:57:50 Re: bug: virtual generated column can be partition key
Previous Message Chao Li 2025-08-25 02:43:49 Re: Identifying function-lookup failures due to argument name mismatches