Re: pgbench - add option to show actual builtin script code - Mailing list pgsql-hackers

From Fabien COELHO
Subject Re: pgbench - add option to show actual builtin script code
Date
Msg-id alpine.DEB.2.21.1907111811060.8895@lancre
Whole thread Raw
In response to Re: pgbench - add option to show actual builtin script code  (Andrew Dunstan <andrew.dunstan@2ndquadrant.com>)
Responses Re: pgbench - add option to show actual builtin script code  (Thomas Munro <thomas.munro@gmail.com>)
List pgsql-hackers
Hello Andrew,

>>> Now the patch is good now.
>>>
>>> The new status of this patch is: Ready for Committer
>
> Why aren't we instead putting the exact scripts in the documentation?
> Having to call pgbench with a special flag to get the script text seems
> a bit odd.

A typical use case I had is to create a new script by modifying an 
existing one for testing or debug. I prefer "command > file.sql ; vi 
file.sql" to hazardous copy-pasting stuff from html pages.

I do not think that it is worth replicating all scripts inside the doc, 
they are not that interesting, especially if more are added. Currently, 
out of the 3 scripts, only one is in the doc, and nobody complained:-)

Now, they could be added to the documentation, but I'd like the option 
anyway.

-- 
Fabien.



pgsql-hackers by date:

Previous
From: Alexander Korotkov
Date:
Subject: Re: Add missing operator <->(box, point)
Next
From: Julien Rouhaud
Date:
Subject: Re: Add parallelism and glibc dependent only options to reindexdb