| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
| Cc: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Asif Rehman <asifr(dot)rehman(at)gmail(dot)com>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: pgbench - allow to create partitioned tables |
| Date: | 2020-01-03 10:51:15 |
| Message-ID: | 84ec8902-4963-948c-452c-b9e2019894f3@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2020-01-03 11:04, Amit Kapila wrote:
> On Fri, Jan 3, 2020 at 3:24 PM Peter Eisentraut
> <peter(dot)eisentraut(at)2ndquadrant(dot)com> wrote:
>>
>> The documentation and pgbench --help output that accompanied this patch
>> claims that the argument to pgbench --partition-method is optional and
>> defaults to "range", but that is not actually the case, as the
>> implementation requires an argument. Could you please sort this out?
>>
>
> AFAICS, if the user omits this argument, then the default is range as
> specified in docs. I tried by using something like 'pgbench.exe -i -s
> 1 --partitions=2 postgres' and then run 'pgbench -S postgres'.
Ah, the way I interpreted this is that the argument to
--partition-method itself is optional.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2020-01-03 10:55:20 | Re: pgbench - use pg logging capabilities |
| Previous Message | Amit Kapila | 2020-01-03 10:04:47 | Re: pgbench - allow to create partitioned tables |