| From: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
|---|---|
| To: | Josh Berkus <josh(at)agliodbs(dot)com> |
| Cc: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>, PostgreSQL Developers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pgbench - allow backslash-continuations in custom scripts |
| Date: | 2015-06-25 16:06:31 |
| Message-ID: | CAMkU=1zBcLtBYJM0fbutMszsz+1NFRqoJ4-SYmK=mfynLd9qpw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Jun 24, 2015 at 1:22 PM, Josh Berkus <josh(at)agliodbs(dot)com> wrote:
> On 06/21/2015 01:37 PM, Fabien COELHO wrote:
> >
> >> The worst case with pgbench is that we break two people's test scripts,
> >> they read the release notes, and fix them.
> >
> > Sure, I agree that breaking pgbench custom scripts compatibility is no
> > big deal, and having pgbench consistent with psql is useful.
>
> ... apparently nobody disagrees ...
>
I'm fine re-punctuating my current scripts. And since pgbench doesn't have
to be version-matched to the server it connects to, people can just keep
using the older version if they want to against a new server.
Are there other breaking changes we have been wanting to make? If so,
should we try to get them all in during the same release?
Cheers,
Jeff
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2015-06-25 16:50:25 | Re: GiST support for UUIDs |
| Previous Message | BRUSSER Michael | 2015-06-25 16:02:33 | Serialization errors in Postgres 9.4.0 |