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

From: Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Stephen Frost <sfrost(at)snowman(dot)net>, Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com>, PostgreSQL Developers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [HACKERS] pgbench - allow to store select results into variables
Date: 2018-10-15 13:09:38
Message-ID: alpine.DEB.2.21.1810151506270.13477@lancre
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: 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.


Attachment Content-Type Size
pgbench-into-21.patch text/x-diff 26.4 KB

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Laurenz Albe 2018-10-15 14:16:02 Re: Function to promote standby servers
Previous Message Fabien COELHO 2018-10-15 13:02:52 Re: pgbench - add pseudo-random permutation function