Re: pgbench: Skipping the creating primary keys after initialization

From: Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>
To: Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pgbench: Skipping the creating primary keys after initialization
Date: 2017-09-19 03:41:49
Message-ID: alpine.DEB.2.20.1709190530560.4792@lancre
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


Hello Masahiko-san,

> Attached the latest version patch incorporated the tap tests.
> Please review it.

Patch applies, compilation & make check ok.

Tests are simple and provide good coverage of new functionalities.

I would suggest to add '--unlogged-tables' so speedup the tests a little.

Comment: "# Custom initialization option, including a space"... ISTM that
there is no space. Space is tested in the next test because of the v's and
the --no-vacuum which turned them into space, which is enough.

Regex are just check for the whole output, so putting twice "qr{vacuum}"
does not check that vacuum appears twice, it checks twice that vacuum
appears once. I do not think that it is worth trying to check for the v
repetition, so I suggest to remove one from the first test. Repetition of
' ' is checked with the second test.

Maybe you could check that the data generation message is there.

--
Fabien.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Pavel Stehule 2017-09-19 03:46:26 Re: PoC plpgsql - possibility to force custom or generic plan
Previous Message Amit Kapila 2017-09-19 03:40:58 Re: Setting pd_lower in GIN metapage