Re: review: pgbench progress report improvements

From: Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>
To: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: review: pgbench progress report improvements
Date: 2013-09-12 15:34:32
Message-ID: alpine.DEB.2.02.1309121729210.3884@localhost6.localdomain6
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


> * patched with minor warning

> some minor issue:
>
> patch warning
>
> make[1]: Leaving directory `/home/pavel/src/postgresql/config'
> [pavel(at)localhost postgresql]$ patch -p1 < pgbench-measurements-v2.patch
> (Stripping trailing CRs from patch; use --binary to disable.)
> patching file contrib/pgbench/pgbench.c
> (Stripping trailing CRs from patch; use --binary to disable.)
> patching file doc/src/sgml/pgbench.sgml

I cannot reproduce these warnings:

postgresql> git branch test
postgresql> git checkout test
Switched to branch 'test'
postgresql> patch -p1 < ../pgbench-measurements-v2.patch
patching file contrib/pgbench/pgbench.c
patching file doc/src/sgml/pgbench.sgml

Some details:

postgresql> patch --version
patch 2.6.1 [...]
postgresql> sha1sum ../pgbench-measurements-v2.patch
f095557ceae1409d2339f9d29d332cefa96e2153 [...]

--
Fabien.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2013-09-12 16:10:01 Re: Triggers on foreign tables
Previous Message Magnus Hagander 2013-09-12 15:33:40 Re: Successor of MD5 authentication, let's use SCRAM