Re: BUG #18386: Slow connection access after 'vacuum full pg_attribute' - Mailing list pgsql-bugs

From Noah Misch
Subject Re: BUG #18386: Slow connection access after 'vacuum full pg_attribute'
Date
Msg-id 20240404052828.52@rfd.leadboat.com
Whole thread Raw
In response to RE: BUG #18386: Slow connection access after 'vacuum full pg_attribute'  ("1165125080" <1165125080@qq.com>)
List pgsql-bugs
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;



pgsql-bugs by date:

Previous
From: David Rowley
Date:
Subject: Re: BUG #18419: Auto Vacuum In PostgreSQL 10.21
Next
From: PG Bug reporting form
Date:
Subject: BUG #18420: Unexpected values appeared in select query statements that should logically imply each other