Re: Add table access method as an option to pgbench - Mailing list pgsql-hackers

From David Zhang
Subject Re: Add table access method as an option to pgbench
Date
Msg-id f051e85f-4248-ce68-c698-e0b5054d960e@highgo.ca
Whole thread Raw
In response to Re: Add table access method as an option to pgbench  (Fabien COELHO <coelho@cri.ensmp.fr>)
List pgsql-hackers
Thanks Fabien for the comments.

On 2020-11-25 11:29 p.m., Fabien COELHO wrote:
>
> Hello David,
>
>> The previous patch was based on branch "REL_13_STABLE". Now, the
>> attached new patch v2 is based on master branch. I followed the new
>> code structure using appendPQExpBuffer to append the new clause
>> "using TABLEAM" in a proper position and tested. In the meantime, I
>> also updated the pgbench.sqml file to reflect the changes.
>
> My 0.02€: I'm fine with the added feature.
>
> The patch lacks minimal coverage test. Consider adding something to
> pgbench tap tests, including failures (ie non existing method).
I added 3 test cases to the tap tests, but not sure if they are
following the rules. One question about the failures test, my thoughts
is that it should be in the no_server test cases, but it is hard to
verify the input as the table access method can be any name, such as
zheap, zedstore or zheap2 etc. Any suggestion will be great.
>
> The option in the help string is not at the right ab place.
Fixed in v3 patch.
>
> I would merge the tableam declaration to the previous one with a
> extended comments, eg "tablespace and access method selection".
Updated in v3 patch.
>
> escape_tableam -> escaped_tableam ?

Updated in v3 patch.

By the way, I saw the same style for other variables, such as
escape_tablespace, should this be fixed as well?

--
David

Software Engineer
Highgo Software Inc. (Canada)
www.highgo.ca




pgsql-hackers by date:

Previous
From: David Zhang
Date:
Subject: Re: Add table access method as an option to pgbench
Next
From: Andy Fan
Date:
Subject: Re: Hybrid Hash/Nested Loop joins and caching results from subplans