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

From 1165125080
Subject RE: BUG #18386: Slow connection access after 'vacuum full pg_attribute'
Date
Msg-id tencent_99422DA984415213F225F6692CE8446CEA08@qq.com
Whole thread Raw
In response to BUG #18386: Slow connection access after 'vacuum full pg_attribute'  (PG Bug reporting form <noreply@postgresql.org>)
Responses Re: BUG #18386: Slow connection access after 'vacuum full pg_attribute'  (Noah Misch <noah@leadboat.com>)
List pgsql-bugs

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.

pgsql-bugs by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Regression tests fail with musl libc because libpq.so can't be loaded
Next
From: Sandeep Thakkar
Date:
Subject: Re: BUG #18408: ERROR: could not load library