From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Tatsuo Ishii <ishii(at)postgresql(dot)org> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Improving pgbench to log index creation time etc. |
Date: | 2013-02-11 14:32:02 |
Message-ID: | 18886.1360593122@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tatsuo Ishii <ishii(at)postgresql(dot)org> writes:
> Hi PostgreSQL hackers,
> I often need to calculate time to spend for index creation and vacuum
> to analyze PostgreSQL data load performance. Index creation and vacuum
> will take non trivial time for large scale data and it is important
> information of data loading benchmark.
> So I would like to propose to add new options to be used with pgbenh
> -i (initialize) mode:
> --log-index-creation-duration: log duration of index creation in seconds
> --log-vacuum-duration: log duration of vacuum in seconds
> What do you think?
I would think if you wanted that, you could set up a custom script that
does CREATE INDEX and/or VACUUM. The built-in scenario isn't all that
interesting...
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Boszormenyi Zoltan | 2013-02-11 14:33:01 | Re: Re: Proposal for Allow postgresql.conf values to be changed via SQL [review] |
Previous Message | Pavel Stehule | 2013-02-11 14:29:23 | Re: Re: proposal: a width specification for s specifier (format function), fix behave when positional and ordered placeholders are used |