Re: Add table access method as an option to pgbench

From: David Zhang <david(dot)zhang(at)highgo(dot)ca>
To: Andres Freund <andres(at)anarazel(dot)de>, Michael Paquier <michael(at)paquier(dot)xyz>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Add table access method as an option to pgbench
Date: 2021-01-20 00:33:47
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

On 2021-01-15 1:22 p.m., Andres Freund wrote:

> Hi,
> On 2020-11-25 12:41:25 +0900, Michael Paquier wrote:
>> On Tue, Nov 24, 2020 at 03:32:38PM -0800, David Zhang wrote:
>>> But, providing another option for the end user may not be a bad idea, and it
>>> might make the tests easier at some points.
>> My first thought is that we have no need to complicate pgbench with
>> this option because there is a GUC able to do that, but we do that for
>> tablespaces, so... No objections from here.
> I think that objection is right. All that's needed to change this from
> the client side is to do something like
> PGOPTIONS='-c default_table_access_method=foo' pgbench ...
Yeah, this is a better solution for me too. Thanks a lot for all the
> I don't think adding pgbench options for individual GUCs really is a
> useful exercise?
> Greetings,
> Andres Freund

Software Engineer
Highgo Software Inc. (Canada)

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jacob Champion 2021-01-20 00:40:07 Re: Support for NSS as a libpq TLS backend
Previous Message Tomas Vondra 2021-01-20 00:07:00 Re: WIP: BRIN multi-range indexes