Re: BUG #18386: Slow connection access after 'vacuum full pg_attribute'

From: Noah Misch <noah(at)leadboat(dot)com>
To: 1165125080 <1165125080(at)qq(dot)com>
Cc: pgsql-bugs <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: BUG #18386: Slow connection access after 'vacuum full pg_attribute'
Date: 2024-04-04 05:28:28
Message-ID: 20240404052828.52@rfd.leadboat.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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;

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message PG Bug reporting form 2024-04-04 06:14:03 BUG #18420: Unexpected values appeared in select query statements that should logically imply each other
Previous Message David Rowley 2024-04-04 01:13:30 Re: BUG #18419: Auto Vacuum In PostgreSQL 10.21