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.1810151506270.13477@lancre
Whole thread Raw
In response to Re: [HACKERS] pgbench - allow to store select results intovariables  (Fabien COELHO <coelho@cri.ensmp.fr>)
Responses Re: [HACKERS] pgbench - allow to store select results into variables  (Alvaro Herrera <alvherre@2ndquadrant.com>)
List pgsql-hackers
> Here is yet another rebase.

Here is yet another rebase after Peter's exit status changes on pgbench.

> Whether Stephen will have time to commit this patch is unclear. I'd suggest 
> that I remove his name from the committer column so that another committer 
> may consider it.
>
> What do you think?

?

> For me this patch is fundamental because it allows a test script to interact 
> both ways with the database, and to act on database data (in particular 
> thanks to \if and expressions already added), and also actually retrieving 
> results is a key benchmark compliance constraint that pgbench does not meet.

-- 
Fabien.
Attachment

pgsql-hackers by date:

Previous
From: Fabien COELHO
Date:
Subject: Re: pgbench - add pseudo-random permutation function
Next
From: Laurenz Albe
Date:
Subject: Re: Function to promote standby servers