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-25 23:45:02 |
Message-ID: | CAB7nPqTDco8rX79Qsr5ZVk0-ePA9oqjgQM3kXLPtanfcKne_PQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Jun 25, 2015 at 10:51 PM, Tatsuo Ishii <ishii(at)postgresql(dot)org> wrote:
>> Look, how many people in the world develop their own pgbench scripts?
>> And how many of those aren't on this list right now, reading this
>> thread? I expect I could count them on my fingers and toes.
>
> 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.
--
Michael
From | Date | Subject | |
---|---|---|---|
Next Message | Tatsuo Ishii | 2015-06-26 00:01:51 | Re: pgbench - allow backslash-continuations in custom scripts |
Previous Message | Michael Paquier | 2015-06-25 23:30:03 | Re: Schedule for 9.5alpha1 |