From: Noah Misch <noah@leadboat.com>
To: 1165125080 <1165125080@qq.com>
Cc: pgsql-bugs <pgsql-bugs@lists.postgresql.org>
Subject: Re: BUG #18386: Slow connection access after 'vacuum full pg_attribute'
Date: Wed, 3 Apr 2024 22:28:28 -0700
Message-ID: <20240404052828.52@rfd.leadboat.com> (raw)
In-Reply-To: <tencent_99422DA984415213F225F6692CE8446CEA08@qq.com>
References: <tencent_99422DA984415213F225F6692CE8446CEA08@qq.com>
On Tue, Mar 26, 2024 at 10:36:31AM +0800, 1165125080 wrote:
> The tuple of the system table is moved to the last part of the pg_attribute
> table by vacuum table. As a result, the connection is slow after the
> database is restarted. Are there any workarounds or suggestions for this
> problem.
System tables have low-numbered attrelid, so I would try this as a workaround
to move them back to the front:
cluster pg_attribute using pg_attribute_relid_attnum_index;
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: noah@leadboat.com, 1165125080@qq.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18386: Slow connection access after 'vacuum full pg_attribute'
In-Reply-To: <20240404052828.52@rfd.leadboat.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox