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 1lrA8v-0007Iv-PW for pgsql-hackers@arkaria.postgresql.org; Thu, 10 Jun 2021 02:10:01 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1lrA8u-00072n-MS for pgsql-hackers@arkaria.postgresql.org; Thu, 10 Jun 2021 02:10:00 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lrA8u-00072f-Ew for pgsql-hackers@lists.postgresql.org; Thu, 10 Jun 2021 02:10:00 +0000 Received: from out1-smtp.messagingengine.com ([66.111.4.25]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lrA8s-0001G2-Ab for pgsql-hackers@postgresql.org; Thu, 10 Jun 2021 02:09:59 +0000 Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.nyi.internal (Postfix) with ESMTP id 53E825C0061; Wed, 9 Jun 2021 22:09:57 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute2.internal (MEProxy); Wed, 09 Jun 2021 22:09:57 -0400 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=fm1; bh=9/EiLvV+2L9LXxa9wpJ9sTzG8pZ G6DdwDTkPc47JYzE=; b=Yxfifu/qGGXfUb4ByKDUHX+uSOc3Qg6k21BCOvJJcmk fr7d6r2Mm0VmCqGeR6tTo1irVNejagvCXZJ9fo2UzuZ/ZCNQy5DJ8axYknh19uE4 UvyXBGTJESwEL+lVv39uoZUlJvkJGosFRdq5AE+673WcHsNScITw2JmfxVFXm5Dq yDot1BrK+58vVV6mxXnmGfhMIlQ+8EX5dfYodaOhnu3jeTJ3rJBKRcAPowuKnEye YYier8AjkjZXK2yF//hSrOG2RCRC6MqQ8l5B8tjpyFlCi7bAyqRGMhmNOHRv+rp8 pbnaEbr5c3nXMwRXGJ7ujKJagBpqUMLuiJhUkLvzx9Q== 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=fm3; bh=9/EiLv V+2L9LXxa9wpJ9sTzG8pZG6DdwDTkPc47JYzE=; b=eLZkCDG0QmbnIeIfGsvJWa ZNKJEKtmC7I5KkfPFju4a8BNSYoUIzbLFLBI1PPqLBhCL9841g72wHKpr62JLAJV LA8IE4Aw1SG5Wxg4ktQj28URVnXGMO5QHF9wY07e47hvaWhAnHuTr9KVTAQOgBfX tYjwvsgYqnGliF53pxnt/7SyptTXtjTUQ8dogKaNn82yu3oTIz1A0bv63xxxY4iz +ZcvKhAnUMumOCw0GOIrJWHlyqEXVw1kRWeaPH9/DaAqQuqFefvva6t8VD8EYhVF hYJk/ho/efM07v3H8xisQ2ZIElQW9qrxIwkyMPNqp9D2BKwATlzQ4TbuFMengpkw == X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrfeduvddgheegucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne gfrhhlucfvnfffucdljedtmdenucfjughrpeffhffvuffkfhggtggujgesghdtreertddt vdenucfhrhhomhepofhitghhrggvlhcurfgrqhhuihgvrhcuoehmihgthhgrvghlsehprg hquhhivghrrdighiiiqeenucggtffrrghtthgvrhhnpedvgeduuefhtdeuleettdevjeeh heeiveeuieegleetgeeljeelieeuieehgeevhfenucevlhhushhtvghrufhiiigvpedtne curfgrrhgrmhepmhgrihhlfhhrohhmpehmihgthhgrvghlsehprghquhhivghrrdighiii X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 9 Jun 2021 22:09:54 -0400 (EDT) Date: Thu, 10 Jun 2021 11:09:52 +0900 From: Michael Paquier To: Tom Lane Cc: Alvaro Herrera , Robert Haas , Dilip Kumar , Andres Freund , pgsql-hackers Subject: Re: Move pg_attribute.attcompression to earlier in struct for reduced size? Message-ID: References: <202106081439.m2pwwk5yvcrd@alvherre.pgsql> <1264790.1623209541@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="8cE3ndIahRVIpYBo" Content-Disposition: inline In-Reply-To: <1264790.1623209541@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --8cE3ndIahRVIpYBo Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Tue, Jun 08, 2021 at 11:32:21PM -0400, Tom Lane wrote: > I can imagine sometime in the future where we need to get rid of all > instances of pglz so we can reassign that compression code to something > else. But would we insist on a mass VACUUM FULL to make that happen? > Doubt it. You'd want a tool that would make that happen over time, > in the background; like the mechanisms that have been discussed for > enabling checksums on-the-fly. Well, I can imagine that some people could afford being more aggressive here even if it implies some downtime and if they are not willing to afford the deployment of a second instance for a dump/restore or a logirep setup. (The parallel with data checksums is partially true, as you can do a switch of checksums with physical replication as the page's checksums are only written when pushed out of shared buffers, not when they are written into WAL. This needs a second instance, of course.) > In the meantime I'm +1 for dropping this logic from VACUUM FULL. > I don't even want to spend enough more time on it to confirm the > different overhead measurements that have been reported. Agreed. It looks like we are heading toward doing just that for this release. -- Michael --8cE3ndIahRVIpYBo Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEG72nH6vTowiyblFKnvQgOdbyQH0FAmDBdHAACgkQnvQgOdby QH1UTQ//VXVpwbQIGxEF+h9AWE8Gai/gokg5651HgQT+ofWnblchRqh4b5zvR0LK ktW30DEHjwR6/OTTDt9qRCG+TORPNDsnGznZ3JbTd9MWh4hOKtlv7lTWrBYTnrfJ RH5SbRE+bpmPH+s4ptlTL1JYU2X2t17eXJwLiLAurzq05iiaaNScZBsNcnKUizkz 6dUQhZWWNy1X+ZUxiakzxfmbL6czaux9J0j/FOMSxcdoIfARltUX72vkFbOS4c+7 9AnQJQc3oUybl4t9CMwi31lj1oIKzhTrX+x3CV1NaqX/+oVau4nK7ULTD8GKK6LK r2B5U1/e+lT9yUm4P9mK3mxmgFZ+vB+BoL9gMVQ+3zYJ/SjEml3HuzdycnFUadvQ /pSqgiziQwW+CYcdUGuGhMAq4/hs6+w7gAjeiroSYuXsRUx5oBzOVO6hGs19KzKj QHhwSADPtgG6ZSwu+CBAIgMXudKdAH6rUJX+YTVo3R1mPCntkiqqNo3EMoVCJd10 aYjqureziibRCJOsaQG6NVb0DI8q7gYXD0MwbfVV5bL4TIfDZTzJAVSk5lcKfoQ1 bFFNKvqsvOMDzBzVIPv504mmlwL59Eppsc/SbCiFUKMZlT5N7zYFAJdBCMh6HYSK DVl1Ufq0JFhjHi68GhTJwn6bKUQ0ZnxbC11SBfyHOTRGR8hTu8k= =cdVY -----END PGP SIGNATURE----- --8cE3ndIahRVIpYBo--