Re: pgbench MAX_ARGS - Mailing list pgsql-hackers

From Andres Freund
Subject Re: pgbench MAX_ARGS
Date
Msg-id 20190226175657.gwht6k4zjn7bsbpb@alap3.anarazel.de
Whole thread Raw
In response to Re: pgbench MAX_ARGS  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On 2019-02-26 12:51:23 -0500, Tom Lane wrote:
> Simon Riggs <simon@2ndquadrant.com> writes:
> > On Tue, 26 Feb 2019 at 17:38, Andres Freund <andres@anarazel.de> wrote:
> >> Why not just allocate it dynamically? Seems weird to have all these
> >> MAX_ARGS, MAX_SCRIPTS ... commands.
> 
> > For me, its a few minutes work to correct a problem and report to the
> > community.
> > Dynamic allocation, run-time errors is all getting too time consuming for a
> > small thing.
> 
> FWIW, I agree --- that's moving the goalposts further than seems
> justified.

I'm fine with applying a patch to just adjust the constant, but I'd also
appreciate somebody just being motivated by my message to remove the
constants ;)


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: pgbench MAX_ARGS
Next
From: Mike Palmiotto
Date:
Subject: Re: [RFC] [PATCH] Flexible "partition pruning" hook