Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gfacz-0005Jj-FS for pgsql-hackers@arkaria.postgresql.org; Sat, 05 Jan 2019 01:19:53 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1gfacx-0003wQ-UL for pgsql-hackers@arkaria.postgresql.org; Sat, 05 Jan 2019 01:19:51 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gfacx-0003wJ-Jw for pgsql-hackers@lists.postgresql.org; Sat, 05 Jan 2019 01:19:51 +0000 Received: from wout2-smtp.messagingengine.com ([64.147.123.25]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gfacv-000065-5W for pgsql-hackers@postgresql.org; Sat, 05 Jan 2019 01:19:50 +0000 Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.west.internal (Postfix) with ESMTP id C267E12C3; Fri, 4 Jan 2019 20:19:47 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Fri, 04 Jan 2019 20:19:48 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=paquier.xyz; h= date:from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=fm3; bh=m724fUwDns/Z1WoM2mqZv3wCZz6 h1nJSs8v1cdG6dfk=; b=sm2lIXYcjf07ntutdiGW0WegDDkOYkN/kTZ4cJehOh9 dRW/54Zx30yRLXpw0ogh2OtXbaLDjxv/5F3Rxy92xhMQA4yH0cAjyfdL7qpr6uZQ Ag5/+80ob3+b3lixCAkEtMmU2fM4HqTwas+LcQBElKIm+/Ze9RjguEDOKElS9KRd 7sC08O7eX+rgwyUiFfGLCd9uQuzWQWHBmll4jTBkPPa9L/y2bgzFVKdN4KphDcD0 JrdzY+c9O3fwzINiMmd3aBq9va0BiC6MA8pDATSFyysWQsrYN93i2nsp2cg4pB9x 6thaFz+MAgc5z12Mnyo7scOoSSXihCNVGVaHXDxAO3Q== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=m724fU wDns/Z1WoM2mqZv3wCZz6h1nJSs8v1cdG6dfk=; b=Gv8KOp7Q4jcSKRMSeZF8rt HS7FU5jGgfvrZj580NFlUA44y67tEdLJp2J4RLxyvs59GhRA5EVkcI0OLgHQC+dz 5cJD6KdlSJKmceBlCzWOMNZChYAkCBffFgDrSrIDqvypz027FAYzP0HOLyiiwP5y YtWI8iVAk5Ht/1L/5yshubEUG7RAbMF+YsimYOZ7fGiFd1QBXVNp8mviqp7zyw8/ tOmwPA1otx7EIoF7eGqGL3URKPcdG1H0aq+LApUdY0M9GYWTIVD0vCPhFDLTpaYL 9Bd7NqxMdeqMmsaoKYBNQfJa5vmdJv8y6/k5FLuZ3rG8E1M4ueBw0+PFXzyzMLCQ == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedtledrvddvgdefheculddtuddrgedtkedrtddtmd cutefuodetggdotefrodftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfhuthen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne gfrhhlucfvnfffucdljedtmdenucfjughrpeffhffvuffkfhggtggujgesghdtreertddt vdenucfhrhhomhepofhitghhrggvlhcurfgrqhhuihgvrhcuoehmihgthhgrvghlsehprg hquhhivghrrdighiiiqeenucfkphepuddukedrvdeguddrvdehtddrfeenucfrrghrrghm pehmrghilhhfrhhomhepmhhitghhrggvlhesphgrqhhuihgvrhdrgiihiienucevlhhush htvghrufhiiigvpedt X-ME-Proxy: Received: from paquier.xyz (mp76f1fa03.ap.nuro.jp [118.241.250.3]) by mail.messagingengine.com (Postfix) with ESMTPA id E55CC100B8; Fri, 4 Jan 2019 20:19:44 -0500 (EST) Date: Sat, 5 Jan 2019 10:19:41 +0900 From: Michael Paquier To: "Bossart, Nathan" Cc: Robert Haas , "pgsql-hackers@postgresql.org" Subject: Re: A few new options for vacuumdb Message-ID: <20190105011941.GD4849@paquier.xyz> References: <20181220020522.GM27104@paquier.xyz> <7B4ACE8E-5D81-416B-B984-17E60F7ABABA@amazon.com> <33F59F9F-78A6-4ECE-BFE0-B1E4AAF40094@amazon.com> <579F2B3A-4EA5-4032-AAD9-4AEE9219A4AB@amazon.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="C+ts3FVlLX8+P6JN" Content-Disposition: inline In-Reply-To: <579F2B3A-4EA5-4032-AAD9-4AEE9219A4AB@amazon.com> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --C+ts3FVlLX8+P6JN Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Fri, Jan 04, 2019 at 11:49:46PM +0000, Bossart, Nathan wrote: > 0004 introduces a slight change to existing behavior. Currently, if > you specify a missing table, vacuumdb will process each table until > it reaches the nonexistent one, at which point it will fail. After > 0004 is applied, vacuumdb will fail during the catalog query, and no > tables will be processed. I have not looked at the patch set in details, but that would make vacuumdb more consistent with the way VACUUM works with multiple relations, which sounds like a good thing. -- Michael --C+ts3FVlLX8+P6JN Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEG72nH6vTowiyblFKnvQgOdbyQH0FAlwwBi0ACgkQnvQgOdby QH2HWg//YP7ksNbvGND8fcndDlyKB4SwXhmb54n4isUHBzCNrS+ZunJGDOQGW2jK WGbK5RhJbQfGFOFQhBEBt3KDJGWH0Ipq9iOCP9Zmcml/bj/krmwl8ww3P54+BvKE c5r5ZbJ8BsDSyasa1MLzR2yX6WnuYU4nE+yfsaPBfHTnbms9dM7eZSTf55Lwx2XP KkaRgTiJACj7sFm31Nb0QnnbWtQVzpPfchkuNOeXkwksGz/gYVbEVyKQobxHAgdq kxLjuvPpTtX0TZjG4YK1dnL58Z9N5l4Fwom3GdZ1WT3XMFpXZ5neEIYqsjrvXo/U PU1drouRpBX8pvZNSUDHykEmRKYrcDYhb+wkmThAyV2Q0wDDJJAZrlaYK5sxrGEr x0K6H29/FEYd5bvZNOIM6RxpA5gX9/c3YPcu/FSgvCsEBWjrUVsu+B8WURH3VcsS HRiyHrz7klj9TvkDk8O/YjFP+Spn/uGqnrmP7ZqUGC1DNoTWU3HHbEycZ+HCjKUC +77NrWIUCqgiyMyUvLHLKsivXK+tqQOs4W/tgqo7XShJNyUBgQjPJ56yEvEEazXG vQxVDYT5XvrP6V54bwCeTPVbT2q+OrboyhPWrNE8yQo/C+RwaFfGSkoZJrt+7n1O XjSkhapTg5bfbc5LvJe9e6Kkfr+0RvKYYsrpZPhlraqHxSaniM8= =l+po -----END PGP SIGNATURE----- --C+ts3FVlLX8+P6JN--