Re: reltuples decreasing with each autovacuum run
濱中 弘和 <hamanaka7767.ita@al.asahi-life.co.jp>
From: 濱中 弘和 <hamanaka7767.ita@al.asahi-life.co.jp>
To: Fujii Masao <masao.fujii@oss.nttdata.com>,
"David G. Johnston" <david.g.johnston@gmail.com>
Cc: "pgsql-bugs@lists.postgresql.org" <pgsql-bugs@lists.postgresql.org>
Date: 2025-05-14T01:28:10Z
Lists: pgsql-bugs
Mr. Masao Fujii Thank you for your reply. I am very grateful for the proposals made so far. I have limited experience with PostgreSQL, and I expected that discussions would advance among those who are knowledgeable within the community, so I did not respond to your feedback. With this premise, I find the second suggestion of "introducing storage parameters that can only be modified by ANALYZE" to be very useful. The reason is that I have AUTOVACUUM operating at a threshold of about 20%. AUTOANALYZE is activated at 10%, and I believe that updating reltuples via AUTOANALYZE alone is sufficient. If there are any tasks I should undertake as the bug reporter, I am willing to put in the effort. Best regards. ________________________________ 差出人: Fujii Masao <masao.fujii@oss.nttdata.com> 送信日時: 2025年5月12日 18:01 宛先: 濱中 弘和 <hamanaka7767.ita@al.asahi-life.co.jp>; David G. Johnston <david.g.johnston@gmail.com> CC: pgsql-bugs@lists.postgresql.org <pgsql-bugs@lists.postgresql.org> 件名: Re: reltuples decreasing with each autovacuum run On 2025/05/02 15:16, 濱中 弘和 wrote: > Dear David J, > Mr. Masao Fujii, > > I apologize for the time that has passed, > but it would be helpful if you could update me on the current situation to determine the future operational policy. > > I understand that this issue has a low priority and is unlikely to be addressed in the near future. > > Could you please confirm if this understanding is correct? I don't think this issue is low priority. However, we haven't reached consensus on any proposed solution yet, and there hasn't been enough discussion on how to address it. Do you have any thoughts on how we might solve this? What do you think about the two ideas I suggested earlier? Regards, -- Fujii Masao Advanced Computing Technology Center Research and Development Headquarters NTT DATA CORPORATION ======================================================================= このE-mailに含まれる情報は、このE-mailの名宛人のみが利用可能な限定された情報です。 万一、当方の誤送信等によりこのE-mailをお受け取りになった場合は、深くお詫び申し上げます。 誠に勝手ではございますが、このメールの印刷、コピー、転送その他 一切のご使用をお控えいただきますようお願いいたします。 お手数をお掛けいたしますが、直ちにこのE-mailを破棄して頂くとともに、誤送信である旨を送信者に通知いただきますようご協力をお願い申し上げます。 ======================================================================= [ex-al]
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Avoid VACUUM reltuples distortion.
- 74388a1ac36d 15.0 cited