Re: [HACKERS] pgbench - allow backslash continuations in \setexpressions - Mailing list pgsql-hackers

From Fabien COELHO
Subject Re: [HACKERS] pgbench - allow backslash continuations in \setexpressions
Date
Msg-id alpine.DEB.2.20.1701131635560.32114@lancre
Whole thread Raw
In response to Re: [HACKERS] pgbench - allow backslash continuations in \set expressions  (Rafia Sabih <rafia.sabih@enterprisedb.com>)
Responses Re: [HACKERS] pgbench - allow backslash continuations in \set expressions  (Rafia Sabih <rafia.sabih@enterprisedb.com>)
List pgsql-hackers
>> Could it be related to transformations operated when the file is downloaded
>> and saved, because it is a text file?
>
> I think this is delaying the patch unnecessarily, I have attached a
> version, please see if you can apply it successfully, we can proceed
> with that safely then...

This is the same file I sent:
 sh> sha1sum pgbench-continuation-4.patch pgbench-continuation-3.patch 97fe805a89707565210699694467f9256ca02dab
pgbench-continuation-4.patch97fe805a89707565210699694467f9256ca02dab  pgbench-continuation-3.patch
 

The difference is that your version is mime-typed with a generic
    Application/OCTET-STREAM

While the one I sent was mime-typed as
    text/x-diff

as defined by the system in /etc/mime.types on my xenial laptop.

My guess is that with the later your mail client changes the file when 
saving it, because it sees "text".

-- 
Fabien.



pgsql-hackers by date:

Previous
From: Stephen Frost
Date:
Subject: Re: [HACKERS] [PATCH] Rename pg_switch_xlog to pg_switch_wal
Next
From: "Daniel Verite"
Date:
Subject: Re: [HACKERS] sequence data type