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

From Thomas Munro
Subject Re: pgbench - add option to show actual builtin script code
Date
Msg-id CA+hUKG+rDo524pc_psC1DUC2Lvxi+D98cqsBF6foh3VNj7BfWw@mail.gmail.com
Whole thread Raw
In response to Re: pgbench - add option to show actual builtin script code  (Fabien COELHO <coelho@cri.ensmp.fr>)
Responses Re: pgbench - add option to show actual builtin script code
List pgsql-hackers
On Fri, Jul 12, 2019 at 4:20 AM Fabien COELHO <coelho@cri.ensmp.fr> wrote:
> >>> 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.

Committed, after pgindent.  Thanks Fabien and Ibrar.

-- 
Thomas Munro
https://enterprisedb.com



pgsql-hackers by date:

Previous
From: Tomas Vondra
Date:
Subject: Re: [Proposal] Table-level Transparent Data Encryption (TDE) and KeyManagement Service (KMS)
Next
From: Tomas Vondra
Date:
Subject: Re: [Proposal] Table-level Transparent Data Encryption (TDE) and KeyManagement Service (KMS)