| From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
|---|---|
| To: | Tatsuo Ishii <ishii(at)postgresql(dot)org> |
| Cc: | Josh Berkus <josh(at)agliodbs(dot)com>, coelho(at)cri(dot)ensmp(dot)fr, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pgbench - allow backslash-continuations in custom scripts |
| Date: | 2015-06-26 00:15:54 |
| Message-ID: | CAB7nPqSgNXVbNLU=Aa-318MKkopwoy_7rS+B1KNBq=82hsqn0A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Jun 26, 2015 at 9:01 AM, Tatsuo Ishii <ishii(at)postgresql(dot)org> wrote:
>>> 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.
I meant "people who can write SQL". Sorry for the misunderstanding.
Please do not take any offense ;)
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2015-06-26 00:53:35 | Re: RFC: replace pg_stat_activity.waiting with something more descriptive |
| Previous Message | Peter Geoghegan | 2015-06-26 00:09:02 | Re: Schedule for 9.5alpha1 |