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 1jyinD-0005rr-KZ for pgsql-novice@arkaria.postgresql.org; Thu, 23 Jul 2020 21:30:19 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1jyinC-00048V-Dj for pgsql-novice@arkaria.postgresql.org; Thu, 23 Jul 2020 21:30:18 +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 1jyinC-00047T-7f for pgsql-novice@lists.postgresql.org; Thu, 23 Jul 2020 21:30:18 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jyinA-0000Nz-8n for pgsql-novice@lists.postgresql.org; Thu, 23 Jul 2020 21:30:17 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 06NLUEIA299366; Thu, 23 Jul 2020 17:30:14 -0400 From: Tom Lane To: Jialun Zhang cc: pgsql-novice@lists.postgresql.org Subject: Re: How to change the default storage strategy for varlena? In-reply-to: References: Comments: In-reply-to Jialun Zhang message dated "Thu, 23 Jul 2020 16:37:48 -0400" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <299364.1595539814.1@sss.pgh.pa.us> Date: Thu, 23 Jul 2020 17:30:14 -0400 Message-ID: <299365.1595539814@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Jialun Zhang writes: > The defualt stroage strategy for varlena is 'x', i.e. EXTENDED. Is there a > way to change it, from either front end or source code? As of v13 you could do something like alter type varchar set (storage = main); (repeat for every varlena type in the system, if that is indeed your desire). This seems like a remarkably bad idea, but it's breaking nobody's database but your own. regards, tom lane