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.96) (envelope-from ) id 1wZjUV-001FGb-0G for pgsql-hackers@arkaria.postgresql.org; Wed, 17 Jun 2026 06:11:11 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1wZjUT-004doF-2I for pgsql-hackers@arkaria.postgresql.org; Wed, 17 Jun 2026 06:11:09 +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.96) (envelope-from ) id 1wZjUT-004dnx-1O for pgsql-hackers@lists.postgresql.org; Wed, 17 Jun 2026 06:11:09 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1wZjUS-00000000lFi-0aRH for pgsql-hackers@lists.postgresql.org; Wed, 17 Jun 2026 06:11:08 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.18.1/8.18.1) with ESMTP id 65H6B1Dg998006; Wed, 17 Jun 2026 02:11:01 -0400 From: Tom Lane To: David Rowley cc: Chao Li , Peter Eisentraut , Andres Freund , Postgres hackers Subject: Re: Fix tuple deformation with virtual generated NOT NULL columns In-reply-to: References: Comments: In-reply-to David Rowley message dated "Wed, 17 Jun 2026 17:04:43 +1200" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <998004.1781676661.1@sss.pgh.pa.us> Date: Wed, 17 Jun 2026 02:11:01 -0400 Message-ID: <998005.1781676661@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk David Rowley writes: >> 2. I can't quite figure out the pattern in these tests for dropping vs >> not dropping the tables at the end of the test. Many tests do DROP >> TABLE and a large number of others don't bother. What's meant to be >> happening here? > I added the DROP TABLE too, as I didn't see any reason mentioned > anywhere that they should be kept. A very rough rule of thumb is that we leave tables around if they might be interesting for the pg_upgrade tests (which try to upgrade the ending state of the core regression tests). regards, tom lane