From: | Elvir Kurić <elvirkuric(at)gmail(dot)com> |
---|---|
To: | David Rowley <david(dot)rowley(at)2ndquadrant(dot)com> |
Cc: | pgsql-performance(at)lists(dot)postgresql(dot)org |
Subject: | Re: "set primary keys..." is missing when using hight values for transactions / scaling factor with pgbench |
Date: | 2018-06-26 12:51:10 |
Message-ID: | CACmNJCHUKNZdPbh7u58niE4EUK8DGATs0ikO4KytjBWpideHog@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
thank you David.
I first run initialize step
$ pgbench -i -s 8000 sampledb
and then run step
$ pgbench -c 10 -j 2 -t 8000 sampledb
if I change -s/-t to lower value , eg, 100 above commands will show
--
set primary keys...
done.
-- -
I am not getting it ,why it fails when I rise -t/-s to 8000 - with same
commands.
Do you suggest that above is not correct way?
On Tue, Jun 26, 2018 at 2:41 PM, David Rowley <david(dot)rowley(at)2ndquadrant(dot)com>
wrote:
> On 27 June 2018 at 00:21, Elvir Kurić <elvirkuric(at)gmail(dot)com> wrote:
> > I have strange issue with pgbench where it fails to execute step to
> create
> > primary keys when I specify scaling factor / transactions to some
> reasonable
> > high value - eg. 8k.
>
> The primary keys are only created in -i mode, which can't be used in
> conjunction with the options you've mentioned.
>
> pgbench will perform a vacuum before an actual test run, so perhaps
> that's what you're seeing. You may also have noticed it also didn't
> perform the create tables and data population too without -i.
>
>
> --
> David Rowley http://www.2ndQuadrant.com/
> PostgreSQL Development, 24x7 Support, Training & Services
>
From | Date | Subject | |
---|---|---|---|
Next Message | David Wheeler | 2018-06-27 03:45:26 | Queue table that quickly grows causes query planner to choose poor plan |
Previous Message | David Rowley | 2018-06-26 12:41:31 | Re: "set primary keys..." is missing when using hight values for transactions / scaling factor with pgbench |