| From: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>, Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com>, Stephen Frost <sfrost(at)snowman(dot)net>, PostgreSQL Developers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [HACKERS] pgbench - allow to store select results into variables |
| Date: | 2018-08-14 20:44:16 |
| Message-ID: | alpine.DEB.2.21.1808142237260.24283@lancre |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
>> I have no doubt that some MUA around would forget to do the conversion.
>
> FWIW, one reason that I invariably use patch(1) to apply submitted patches
> is that it will take care of stripping any CRs that may have snuck in.
> So I'm not particularly fussed about the problem.
Good to know.
> I'm not excited about encouraging people to use application/octet-stream
> rather than text/something for submitted patches.
I'm not happy with that either, it is just to avoid complaints.
> If you use text then the patch can easily be examined in the web
> archives; with application/octet-stream the patch has to be downloaded,
> adding a lot of manual overhead.
Indeed.
> (At least, that's true with my preferred web browser, maybe it's
> different for other people?)
So if I send with text/x-diff or text/plain I've got complaints, if I send
with application/octet-stream, it is not right either:-) Everybody being
somehow right.
Sigh.
--
Fabien.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2018-08-14 20:53:11 | Re: [HACKERS] pgbench - allow to store select results into variables |
| Previous Message | Peter Geoghegan | 2018-08-14 20:43:07 | Re: Pre-v11 appearances of the word "procedure" in v11 docs |