Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pGTPJ-0006xM-PS for pgsql-hackers@arkaria.postgresql.org; Fri, 13 Jan 2023 23:24:21 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pGTPI-0000rA-9u for pgsql-hackers@arkaria.postgresql.org; Fri, 13 Jan 2023 23:24:20 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pGTPH-0000r1-Ss for pgsql-hackers@lists.postgresql.org; Fri, 13 Jan 2023 23:24:20 +0000 Received: from mail-pg1-x533.google.com ([2607:f8b0:4864:20::533]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1pGTPB-0006dn-BQ for pgsql-hackers@postgresql.org; Fri, 13 Jan 2023 23:24:19 +0000 Received: by mail-pg1-x533.google.com with SMTP id d10so15953467pgm.13 for ; Fri, 13 Jan 2023 15:24:12 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=j-davis-com.20210112.gappssmtp.com; s=20210112; h=mime-version:user-agent:content-transfer-encoding:references :in-reply-to:date:to:from:subject:message-id:from:to:cc:subject:date :message-id:reply-to; bh=1v/NvCxyur8g3c/VguQYnamwZDKmY/EazY1NGLDcu+8=; b=Rhm1c8fPX2jfrcwoN3uHnjRX4IAnM0+plduNHXGe3n+jE/bOypcP+HHuytjGibCJcb ndQa0LyWevlkZ9DxrsxfwkMgDCilgRDZMwIm12gyR6eHRsID2bZ626BrutU1QDJt19OQ HtvApaa3a12Z8SKxFeszLg2xMkLpQNI37tTDv3hSUKeprtOEI4f+UBA4lOBkiXd32XDm ngdOHOyuZYXPsWHX9VFkR+YVH6/dBReP226BK2JiKJSy7HrZyniwmcVtjJ3IMDcIXUjZ /hSBpDlPrySq2i7kmzvEZtJJVahbXTLWiAwL8VxbMPExq5FuOgEIEJyxBCFaCqQ1kpjc U5RA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=mime-version:user-agent:content-transfer-encoding:references :in-reply-to:date:to:from:subject:message-id:x-gm-message-state:from :to:cc:subject:date:message-id:reply-to; bh=1v/NvCxyur8g3c/VguQYnamwZDKmY/EazY1NGLDcu+8=; b=pcRsAmoQY95inj+gQvf+NO7qAAy2cR3JRkvvZAnOO+ddd68WsTf5x3eAdI3iTNm/m0 0QQbOGX+Gsl6SHdjuMEifozVloqZqp8Njt8HHozv7Vd+gPEoTfBnqR5X/Y/M/v0hP4MK yrgS3PCnuvwRrlVZ4LXTcM++se8Vw4zziEa9XGpdFg0hwr/4GOH/Gd0AvfizaunJCfXR xDNmAJXJVqopNIK0kcJholQYDk0ZEDiJqBucHGgn/EMy0vpZkH7AYespBzlAbqmmQBxZ TrUUVepvFH3SDIWv1JqrMffr9L05P9jfoxvmLFC/l82/Vi6Ij73+la33KxQGCOKb+jZE OCsg== X-Gm-Message-State: AFqh2kpamsD0xJFDrGYUSwmYCVQlJtac6DzWQumStQ3VQHtIeEeDBWm5 Cg/zHq731+PNdUC1xd2/zRyjYQ== X-Google-Smtp-Source: AMrXdXvexPABS1eKcsbgUCDeDBgxCBJxvf4PrQbojdcQe/4My6RnMMCfpkSEq9i0pG0ZnWwKqGSx2Q== X-Received: by 2002:a62:7b11:0:b0:586:e399:9cd4 with SMTP id w17-20020a627b11000000b00586e3999cd4mr11765123pfc.25.1673652251014; Fri, 13 Jan 2023 15:24:11 -0800 (PST) Received: from jeff-laptop.lan (c-73-231-146-4.hsd1.ca.comcast.net. [73.231.146.4]) by smtp.gmail.com with ESMTPSA id z13-20020aa79e4d000000b0058bc1a13ffcsm809004pfq.25.2023.01.13.15.24.10 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 13 Jan 2023 15:24:10 -0800 (PST) Message-ID: Subject: Re: add PROCESS_MAIN to VACUUM From: Jeff Davis To: Nathan Bossart , pgsql-hackers@postgresql.org Date: Fri, 13 Jan 2023 15:24:09 -0800 In-Reply-To: <20221230000028.GA435655@nathanxps13> References: <20221230000028.GA435655@nathanxps13> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable User-Agent: Evolution 3.44.4-0ubuntu1 MIME-Version: 1.0 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Thu, 2022-12-29 at 16:00 -0800, Nathan Bossart wrote: > The motivation for adding this option is to make it easier to VACUUM > only a > relation's TOAST table.=C2=A0 At the moment, you need to find the TOAST > table by > examining a relation's reltoastrelid, and you need USAGE on the > pg_toast > schema.=C2=A0 This option could also help make it possible to call only > vac_update_datfrozenxid() without processing any relations, as > discussed > elsewhere [2]. For completeness, did you consider CLUSTER and REINDEX options as well? --=20 Jeff Davis PostgreSQL Contributor Team - AWS