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 1sEidu-003C2t-LG for pgsql-hackers@arkaria.postgresql.org; Wed, 05 Jun 2024 04:53:00 +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 1sEids-0051wM-Cj for pgsql-hackers@arkaria.postgresql.org; Wed, 05 Jun 2024 04:52:56 +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 1sEids-0051wE-1U for pgsql-hackers@lists.postgresql.org; Wed, 05 Jun 2024 04:52:56 +0000 Received: from wfout7-smtp.messagingengine.com ([64.147.123.150]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sEidk-003Wfy-FU for pgsql-hackers@lists.postgresql.org; Wed, 05 Jun 2024 04:52:54 +0000 Received: from compute2.internal (compute2.nyi.internal [10.202.2.46]) by mailfout.west.internal (Postfix) with ESMTP id B675B1C0010E; Wed, 5 Jun 2024 00:52:45 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute2.internal (MEProxy); Wed, 05 Jun 2024 00:52:46 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=paquier.xyz; h= cc:cc:content-type:content-type:date:date:from:from:in-reply-to :in-reply-to:message-id:mime-version:references:reply-to:subject :subject:to:to; s=fm1; t=1717563165; x=1717649565; bh=7URtLK0VxO Fs7Hu84xN1vZXQPVCpSqne+IPvVwnXy/Y=; b=WA5GVZshF4vV3mmQ5prrRe3H0L XYseYb1esrHVraYq9Posn9GwF7GhWd5EJXOMtrxo6Go0PNkkN8fKB7tEtSGafZ7w swKSriFLE5UX7eiuPCJy7MC9vM1/T6RPtXJumRHEiqejJ6lWEmC7/B1ITJR0R1QX 0GwvYzTAwEXGomjA3CCwj1/UVzsp0B+oWrmxxTc89u3aevNZrY7LriF+Bj/j5s8c Jw6Gf7KXqNtY6SZ2QCqXQYaHWHSQ4VkCjNaKxj9mGFK/ISWLYXM8CfLR5oIKXxXJ /gSKCM26gzk4tyuwJR5ngNGy4Jeg98C5hBWpVW1yswFlm71fqMqB86Y67aaA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-type:content-type:date:date :feedback-id:feedback-id:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:subject:subject:to :to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s= fm1; t=1717563165; x=1717649565; bh=7URtLK0VxOFs7Hu84xN1vZXQPVCp Sqne+IPvVwnXy/Y=; b=Epx93gM4azAHj9UGPKILfnU062sZsmAvLvse9wP8Jqjn WHEW9oVRe+YBKhxeRbLNsTbuwFsJpR6zLDWEidwQ3SWimdV7Zad1bhQnUoACd3O6 XbPlMiW8YMOPsLZEpW/nwh537pLyvKeHcUcDfVxYGLIPL0hFT9AzO4IXmBIStQkh /BHKLKenMAcARnwpvxIv78UZi7zXq5fKwFKskXl2CU3QerX8sYolwPoeqMW6aoWQ N8v+DdKynw8QpImWYzCPdz1AtHCbTFf3LR3xVdJnuyS0dVDUT1zhZE/UNoX9qbFK 4S+OX4/V3ivsRfIaHyoII3zD8YyYg0gNheuB1PzMTw== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvledrvdelhedgkeekucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne gfrhhlucfvnfffucdlfeehmdenucfjughrpeffhffvvefukfhfgggtuggjsehgtderredt tddvnecuhfhrohhmpefoihgthhgrvghlucfrrghquhhivghruceomhhitghhrggvlhesph grqhhuihgvrhdrgiihiieqnecuggftrfgrthhtvghrnhepgeffjeevgfevuddvjedtvddt ieejheduueelvddufedtgfefjedvkeevkeeivddvnecuffhomhgrihhnpehpohhsthhgrh gvshhqlhdrohhrghenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhl fhhrohhmpehmihgthhgrvghlsehprghquhhivghrrdighiii X-ME-Proxy: Feedback-ID: i0fe9450f:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 5 Jun 2024 00:52:40 -0400 (EDT) Date: Wed, 5 Jun 2024 13:52:21 +0900 From: Michael Paquier To: Nathan Bossart Cc: Kyotaro Horiguchi , postgres@jeltef.nl, smithpb2250@gmail.com, vignesh21@gmail.com, jakub.wartak@enterprisedb.com, stark.cfm@gmail.com, hlinnaka@iki.fi, barwick@gmail.com, jchampion@timescale.com, pryzby@telsasoft.com, tgl@sss.pgh.pa.us, rjuju123@gmail.com, jakub.wartak@tomtom.com, pgsql-hackers@lists.postgresql.org, bharath.rupireddyforpostgres@gmail.com Subject: Re: In-placre persistance change of a relation Message-ID: References: <20240524.160916.2199777355532445323.horikyota.ntt@gmail.com> <20240604.160032.391318120410028809.horikyota.ntt@gmail.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="FpxxFf0p30jaW0cw" Content-Disposition: inline In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --FpxxFf0p30jaW0cw Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Tue, Jun 04, 2024 at 03:50:51PM -0500, Nathan Bossart wrote: > Bharath, does the multi-INSERT stuff apply when changing a table to be > LOGGED? If so, I think it would be interesting to compare it with the FPI > approach being discussed here. The answer to this question is yes AFAIK. Look at patch 0002 in the latest series posted here, that touches ATRewriteTable() in tablecmds.c where the rewrite happens should a relation's relpersistence, AM, column or default requires a switch (particularly if more than one property is changed in a single command, grep for AT_REWRITE_*): https://www.postgresql.org/message-id/CALj2ACUz5+_YNEa4ZY-XG960_oXefM50MjD71VgSCAVDkF3bzQ@mail.gmail.com I've just read through the patch set, and they are rather pleasant to the eye. I have comments about them, actually, but that's a topic for the other thread. -- Michael --FpxxFf0p30jaW0cw Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEG72nH6vTowiyblFKnvQgOdbyQH0FAmZf7wUACgkQnvQgOdby QH2VFRAAmpiNwKoUu+iWDVwS+SEM0Zer36oHOIq3NRyJOaYc4PvzK6Ys+OLFJ5M/ L0QZvXSS4sklb4/2LZx+yy7tnbfKjemPWykkiYRTAZ5AbTcramGkts5vZIk7H42U osNT/dEsTYpO0rAbdpJks3rQaxCHpX+P+au6SgtzbjoHy4dBZ+MWEo0vviJaXpoS KfLKpEi22HlFg48oY6UMAq+zEkTciWxAfkBxCFFCkVB3OoNMWrtYKs+Xf2pNyI27 KwsB9BdREmZeKeixPw6Y0sV1m3L8NuPxbrErHJSVgVO/DCDFc9LmLSIeyfe1IA9r ie7iGhgcX7mPmCrJT2PC3VXkgza1R7lBpMpQLwMUQWeltRIMKEQCdXLVRaLGqc/e g4V0Jnf4gZMcWavw3Grn+SKxQS2Hk2cU10FLuCiT8AtoQwQy0kxPDQLwMLvGRsIV HJUX7Lv4QI3YNpeVI7DNpnGZ/zBKf3710XLnKznhaev+wVGVSJTdOSPt5o7p/dQK b2igcTvv3v76jvfDW+YmlPWxa/lIFFXVudr5CNlbiquywcUDguQQpS6pznJi2xZl KlNvQ4yOlYneA840zbE3hYxJgmRiobaTZUuzcnLXOtZ9t1QyflT0FOIKiSKFR1Hd +Xc/OhshyOvBoZWV//BpMQDjDuX+52gUhdBjDls1Izs9DhnKMLg= =BGsW -----END PGP SIGNATURE----- --FpxxFf0p30jaW0cw--