Re: [HACKERS] pgbench - allow to store select results intovariables - Mailing list pgsql-hackers

From Fabien COELHO
Subject Re: [HACKERS] pgbench - allow to store select results intovariables
Date
Msg-id alpine.DEB.2.21.1808140012360.2727@lancre
Whole thread Raw
In response to Re: [HACKERS] pgbench - allow to store select results into variables  (Andrew Dunstan <andrew.dunstan@2ndquadrant.com>)
Responses Re: [HACKERS] pgbench - allow to store select results into variables
List pgsql-hackers
Hello Andrew,

>> Attached is v18, another basic rebase after some perl automatic 
>> reindentation.
>
> This patch contains CRLF line endings

Alas, not according to "file" nor "hexdump" (only 0A, no 0D) on my local 
version, AFAICS.

What happens on the path and what is done by mail clients depending on the 
mime type is another question (eg text/x-diff or text/plain).

> - and in any case it doesn't apply any more. Please fix those things.

Here is the new generated version, v19, that I just tested on my linux 
ubuntu bionic laptop:

   sh> git checkout -b test master
   Switched to a new branch 'test'

   sh> cksum ~/pgbench-into-19.patch
   3375461661 26024 ~/pgbench-into-19.patch

   sh> hexdump ~/pgbench-into-19.patch
   0000000 6964 6666 2d20 672d 7469 6120 642f 636f
   0000010 732f 6372 732f 6d67 2f6c 6572 2f66 6770
   0000020 6562 636e 2e68 6773 6c6d 6220 642f 636f
   0000030 732f 6372 732f 6d67 2f6c 6572 2f66 6770
   0000040 6562 636e 2e68 6773 6c6d 690a 646e ....
   # no 0d in front of 0a             ^^

   sh> git apply ~/pgbench-into-19.patch

   sh>  git status
   On branch test ...
         modified:   doc/src/sgml/ref/pgbench.sgml
         modified:   src/bin/pgbench/pgbench.c
         modified:   src/bin/pgbench/pgbench.h
         modified:   src/bin/pgbench/t/001_pgbench_with_server.pl
         modified:   src/fe_utils/psqlscan.l
         modified:   src/include/fe_utils/psqlscan_int.h

-- 
Fabien.
Attachment

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: libpq should append auth failures, not overwrite
Next
From: Peter Geoghegan
Date:
Subject: Pre-v11 appearances of the word "procedure" in v11 docs