| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Simon Riggs <simon(at)2ndquadrant(dot)com>, Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: pgbench MAX_ARGS |
| Date: | 2019-02-26 17:56:57 |
| Message-ID: | 20190226175657.gwht6k4zjn7bsbpb@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2019-02-26 12:51:23 -0500, Tom Lane wrote:
> Simon Riggs <simon(at)2ndquadrant(dot)com> writes:
> > On Tue, 26 Feb 2019 at 17:38, Andres Freund <andres(at)anarazel(dot)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 ;)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mike Palmiotto | 2019-02-26 18:06:31 | Re: [RFC] [PATCH] Flexible "partition pruning" hook |
| Previous Message | Tom Lane | 2019-02-26 17:51:23 | Re: pgbench MAX_ARGS |