From: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
---|---|
To: | Rafia Sabih <rafia(dot)sabih(at)enterprisedb(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL Developers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: pgbench - allow backslash continuations in \set expressions |
Date: | 2017-01-13 11:27:57 |
Message-ID: | alpine.DEB.2.20.1701131130180.32114@lancre |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hello Rafia,
>> sh> git apply ~/pgbench-continuation-3.patch
>> # ok
>
> It still gives me whitespace errors with git apply,
Strange.
> /Users/edb/Downloads/pgbench-continuation-3.patch:31: trailing whitespace.
> continuation \\{newline}
> Looks like an editor issue, I used awk '{ sub("\r$", ""); print }'
> patch1 > patch2 to clean it and it was applying then.
Doing that does not change the file for me.
I see no \r in the patch file according to "od", I just see "nl" (0x0a).
sha1sum: 97fe805a89707565210699694467f9256ca02dab pgbench-continuation-3.patch
Could it be related to transformations operated when the file is
downloaded and saved, because it is a text file?
--
Fabien.
From | Date | Subject | |
---|---|---|---|
Next Message | Amit Khandekar | 2017-01-13 11:38:05 | Too many autovacuum workers spawned during forced auto-vacuum |
Previous Message | Etsuro Fujita | 2017-01-13 11:22:45 | Re: postgres_fdw bug in 9.6 |