Re: pgbench: Skipping the creating primary keys after initialization
Masahiko Sawada <sawada.mshk@gmail.com>
From: Masahiko Sawada <sawada.mshk@gmail.com>
To: Fabien COELHO <coelho@cri.ensmp.fr>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Robert Haas <robertmhaas@gmail.com>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2017-09-08T00:52:48Z
Lists: pgsql-hackers
On Thu, Sep 7, 2017 at 4:15 PM, Fabien COELHO <coelho@cri.ensmp.fr> wrote: > >>> Very very minor comments that I should have noticed before, sorry for >>> this >>> additional round trip. >> >> >> Thank you for the dedicated review! > > > I'm someone at times pigheaded, I think in the good sense if it is possible, > and I like to finish what I start:-) > > Patch applies, compiles, works, everything is fine from my point of view. > > I switched it to "Ready for Committer". Thanks. > > Again, if the pgbench tap test patch get through, it should be tap tested. > Thank you for the remainder, I'll add tap tests once the patch got committed. -- Regards, -- Masahiko Sawada NIPPON TELEGRAPH AND TELEPHONE CORPORATION NTT Open Source Software Center
Commits
-
Allow running just selected steps of pgbench's initialization sequence.
- 591c504fad0d 11.0 landed