Re: pgbench MAX_ARGS - Mailing list pgsql-hackers

From Andres Freund
Subject Re: pgbench MAX_ARGS
Date
Msg-id 20190226173758.lh3zpukwijvbjvkg@alap3.anarazel.de
Whole thread Raw
In response to Re: pgbench MAX_ARGS  (Simon Riggs <simon@2ndquadrant.com>)
Responses Re: pgbench MAX_ARGS  (Simon Riggs <simon@2ndquadrant.com>)
List pgsql-hackers
Hi,

On 2019-02-26 12:57:14 +0000, Simon Riggs wrote:
> On Tue, 26 Feb 2019 at 12:19, Fabien COELHO <coelho@cri.ensmp.fr> wrote:
> I've put it as 256 args now.
> 
> The overhead of that is about 2kB, so not really an issue.

Why not just allocate it dynamically? Seems weird to have all these
MAX_ARGS, MAX_SCRIPTS ... commands. The eighties want their constants
back ;)

Greetings,

Andres Freund


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Remove Deprecated Exclusive Backup Mode
Next
From: Tom Lane
Date:
Subject: Re: No-rewrite timestamp<->timestamptz conversions