Date: Tue, 15 Aug 2023 08:34:23 -0700
From: Nathan Bossart <nathandbossart@gmail.com>
To: Fabien COELHO <coelho@cri.ensmp.fr>
Cc: Hannu Krosing <hannuk@google.com>,
	pgsql-hackers <pgsql-hackers@postgresql.org>,
	Dimitri Fontaine <dim@tapoueh.org>
Subject: Re: pgbench - adding pl/pgsql versions of tests
Message-ID: <20230815153423.GB2296544@nathanxps13>
References: <CAMT0RQR1TNSnSWwd65is=HCDjiP4i25mcDDoctEBEiV8351cMQ@mail.gmail.com>
 <20230814150737.GA1395427@nathanxps13>
 <d01513e9-8c19-da5-fabc-845f75377f52@mines-paristech.fr>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <d01513e9-8c19-da5-fabc-845f75377f52@mines-paristech.fr>
Archived-At: <https://www.postgresql.org/message-id/20230815153423.GB2296544%40nathanxps13>
Precedence: bulk

On Tue, Aug 15, 2023 at 09:46:59AM +0200, Fabien COELHO wrote:
> I'm unclear about what variety of scripts that could be provided given the
> tables made available with pgbench. ISTM that other scenari would involve
> both an initialization and associated scripts, and any proposal would be
> bared because it would open the door to anything.

Why's that?  I'm not aware of any project policy that prohibits such
enhancements to pgbench.  It might take some effort to gather consensus on
a proposal like this, but IMHO that doesn't mean we shouldn't try.  If the
prevailing wisdom is that we shouldn't add more built-in scripts because
there is an existing way to provide custom ones, then it's not clear that
we should proceed with $SUBJECT, anyway.

-- 
Nathan Bossart
Amazon Web Services: https://aws.amazon.com