Horton

Re: [HACKERS] pgbench - allow to store select results into variables

Andrew Gierth <andrew@tao11.riddles.org.uk>

View thread View on postgr.es
From: Andrew Gierth <andrew@tao11.riddles.org.uk>
To: Andrew Dunstan <andrew.dunstan@2ndquadrant.com>
Cc: Fabien COELHO <coelho@cri.ensmp.fr>, Stephen Frost <sfrost@snowman.net>, PostgreSQL Developers <pgsql-hackers@postgresql.org>
Date: 2018-08-14T12:43:32Z
Lists: pgsql-hackers 
>>>>> "Andrew" == Andrew Dunstan <andrew.dunstan@2ndquadrant.com> writes:

 >> The patch in the original email is in text/plain with base64 transfer
 >> encoding, which means that CRLF line endings are mandatory. It's
 >> actually up to the receiving MUA (or the archives webserver) to undo
 >> that.
 >> 
 >> If the archives webserver isn't handling that then it's a bug there.

 Andrew> Probably a good reason not to use text/plain for patches, ISTM.
 Andrew> I do note that my MUA (Thunderbird) uses text/x-patch and
 Andrew> probably violates RFC2046 4.1.1

The first patch of yours I found was in text/x-patch with 7bit transfer
encoding, so the line endings are actually those of the mail message
itself (i.e. CRLF on the wire).

-- 
Andrew (irc:RhodiumToad)

Commits

  1. pgbench: Remove \cset

  2. pgbench: add \cset and \gset commands

  3. Adjust pgbench to allow non-ASCII characters in variable names.

  4. Refactor script execution state machine in pgbench.

  5. Allow empty queries in pgbench.