Content-Type: text/plain;
	charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3776.700.51.11.1\))
Subject: Re: Test to dump and restore objects left behind by regression
From: Daniel Gustafsson <daniel@yesql.se>
In-Reply-To: <202503281812.33bmlx2yuy7w@alvherre.pgsql>
Date: Mon, 31 Mar 2025 23:17:15 +0200
Cc: Tom Lane <tgl@sss.pgh.pa.us>,
 Ashutosh Bapat <ashutosh.bapat.oss@gmail.com>,
 Michael Paquier <michael@paquier.xyz>,
 vignesh C <vignesh21@gmail.com>,
 Peter Eisentraut <peter@eisentraut.org>,
 PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Content-Transfer-Encoding: 7bit
Message-Id: <730EAD98-E876-4706-A9B0-4606ACB1B85B@yesql.se>
References: <202503281812.33bmlx2yuy7w@alvherre.pgsql>
To: Alvaro Herrera <alvherre@alvh.no-ip.org>
Archived-At: 
 <https://www.postgresql.org/message-id/730EAD98-E876-4706-A9B0-4606ACB1B85B%40yesql.se>
Precedence: bulk

> On 28 Mar 2025, at 19:12, Alvaro Herrera <alvherre@alvh.no-ip.org> wrote:
> 
> On 2025-Mar-28, Tom Lane wrote:
> 
>> I think instead of going this direction, we really need to create a
>> separately-purposed script that simply creates "one of everything"
>> without doing anything else (except maybe loading a little data).
>> I believe it'd be a lot easier to remember to add to that when
>> inventing new SQL than to remember to leave something behind from the
>> core regression tests.  This would also be far faster to run than any
>> approach that involves picking a random subset of the core test
>> scripts.
> 
> FWIW this sounds closely related to what I tried to do with
> src/test/modules/test_ddl_deparse; it's currently incomplete, but maybe
> we can use that as a starting point.

Given where we are in the cycle, it seems to make sense to stick to using the
schedule we already have rather than invent a new process for generating it,
and work on that for 19?

--
Daniel Gustafsson