From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: pgbench: Skipping the creating primary keys after initialization |
Date: | 2017-08-02 13:25:45 |
Message-ID: | CA+TgmoboLBOGDxoj5YEZNUpGVwsmj779taEg_ec_5NDJDJ=8xQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Aug 1, 2017 at 9:49 PM, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com> wrote:
> I'd like to propose a new option -I for pgbench command which skips
> the creating primary keys after initialized tables. This option is
> useful for users who want to do bench marking with no index or indexes
> other than btree primary index. If we initialize pgbench tables at a
> large number scale factor the primary key index creation takes a long
> time even if we're going to use other types of indexes. With this
> option, the initialization time is reduced and you can create indexes
> as you want.
>
> Feedback is very welcome. I'll add this patch to the next CF.
I support adding an option for this, but I propose that we just make
it a long-form option, similar to --log-prefix or --index-tablespace.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Masahiko Sawada | 2017-08-02 13:38:19 | Re: pgbench: Skipping the creating primary keys after initialization |
Previous Message | Robert Haas | 2017-08-02 12:22:02 | Re: Confusing error message in pgbench |