| From: | Tatsuo Ishii <ishii(at)postgresql(dot)org> |
|---|---|
| To: | michael(dot)paquier(at)gmail(dot)com |
| Cc: | josh(at)agliodbs(dot)com, coelho(at)cri(dot)ensmp(dot)fr, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: pgbench - allow backslash-continuations in custom scripts |
| Date: | 2015-06-26 00:01:51 |
| Message-ID: | 20150626.090151.571739936771472144.t-ishii@sraoss.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
>> I'm not against you break the backward compatibility of pgbench custom
>> scripts.
>>
>> However I just want to let you know that PostgreSQL Enterprise
>> Consortium has been published couple of scripts along with reports on
>> evaluating PostgreSQL, which have been downloaded considerable
>> numbers.
>
> pgbench is a tool for dedicated to developers. Hence people who should
> be able to fix scripts properly as long as we inform them by
> documenting it in the release notes so I am not sure that this is
> actually a problem.
I'm not sure what you mean by "developers" here but if that means
people who are developing PostgreSQL itself, I am strongly against
"pgbench is a tool for dedicated to developers" concept. Pgbench has
been heavily used by users who want to measure PostgreSQL's
performance.
Best regards,
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese:http://www.sraoss.co.jp
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2015-06-26 00:08:18 | Re: git push hook to check for outdated timestamps |
| Previous Message | Michael Paquier | 2015-06-25 23:45:02 | Re: pgbench - allow backslash-continuations in custom scripts |