Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rsFeO-005pAu-UR for pgsql-bugs@arkaria.postgresql.org; Thu, 04 Apr 2024 05:28:37 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1rsFeN-00FO4c-L2 for pgsql-bugs@arkaria.postgresql.org; Thu, 04 Apr 2024 05:28:35 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rsFeN-00FO2r-4z for pgsql-bugs@lists.postgresql.org; Thu, 04 Apr 2024 05:28:35 +0000 Received: from mail-yw1-x1136.google.com ([2607:f8b0:4864:20::1136]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1rsFeK-000TfI-9s for pgsql-bugs@lists.postgresql.org; Thu, 04 Apr 2024 05:28:33 +0000 Received: by mail-yw1-x1136.google.com with SMTP id 00721157ae682-615019cd427so5682877b3.3 for ; Wed, 03 Apr 2024 22:28:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=leadboat.com; s=google; t=1712208511; x=1712813311; darn=lists.postgresql.org; h=user-agent:in-reply-to:content-disposition:mime-version:references :message-id:subject:cc:to:from:date:from:to:cc:subject:date :message-id:reply-to; bh=4jImCIWKWSuiZHh3cwXzi5+DaxGEocoIsyRm0v9Rduc=; b=VQ8gQPQXYZ8Jcc/NTU/9BlH1Cpm17v1OP9z+DWR9KHpw3vWoBW5ahYhgKJwKQrh/dr jNaoAhsVSBEp101zdCFZGBXu6uo9LcLTBoQMDvPOQrh1whUiqD0YwOZxFnnncac98Yfd 0fe72CUvM2dN7Xfm+79qzm4MtyXMHNmsc2uK8= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1712208511; x=1712813311; h=user-agent:in-reply-to:content-disposition:mime-version:references :message-id:subject:cc:to:from:date:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=4jImCIWKWSuiZHh3cwXzi5+DaxGEocoIsyRm0v9Rduc=; b=HoeR9guMxHb0gWuJHydIJZoFrYzosDX04dKNIgX5SsVVyXGH5VIBylXm68eZZPfn7t wBkfn15ao26PcDUQe2YNzDjG1qH240yv9VJsh4nOSp0fuC3mFRYlK/9mPqftEbigQi4s yYMBsLLQSnSpgMBDPHJaRudKhtWiNRCIosdjy7TqtvHr1sT/Xi5UApG3AQC+AZX8nurL bB/BFe7u4J+qP9rRyATdchk8F9h0bAvjdk/Z1A/gVviPbMdJDO1P+/Upp/o4Q44UXBKZ XVwZevolB3bn+oqLDII0N0vL8JPpYW7oxxlFUjaGAO1+16CSN2UIqsxALvoXnLQk3Ahe 2QIw== X-Gm-Message-State: AOJu0YzI8ggo7RCaInXXpKkBrS4LL6sv3qQFZVyae4YPUn4Ka7WbVn3a w8TpnocWUkfqbZZE7PdG+qB/S8ExgOl5hqILrKPW57TrWRqvV0HaM0TNRzGenBInB4Z9H7zdwrU = X-Google-Smtp-Source: AGHT+IHtvh32Jcj5W1GOMmAgkCra2cfCj03zVZ6/F/Kv9ZpOsniYtk0NXextJ4qDvtSeq9yd+2VxHA== X-Received: by 2002:a0d:ea46:0:b0:615:41a4:1a8a with SMTP id t67-20020a0dea46000000b0061541a41a8amr1402373ywe.25.1712208511339; Wed, 03 Apr 2024 22:28:31 -0700 (PDT) Received: from rfd.leadboat.com ([2600:1702:a20:5750::48]) by smtp.gmail.com with ESMTPSA id n6-20020a81af06000000b006156ced7476sm559961ywh.62.2024.04.03.22.28.30 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 03 Apr 2024 22:28:30 -0700 (PDT) Date: Wed, 3 Apr 2024 22:28:28 -0700 From: Noah Misch To: 1165125080 <1165125080@qq.com> Cc: pgsql-bugs Subject: Re: BUG #18386: Slow connection access after 'vacuum full pg_attribute' Message-ID: <20240404052828.52@rfd.leadboat.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/2.2.12 (2023-09-09) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk 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;