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-02 06:43:04
Message-ID: alpine.DEB.2.21.1810020832440.27693@lancre
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

Bonjour Michaël,

> On Tue, Aug 14, 2018 at 01:38:21PM +0200, Fabien COELHO wrote:
>> I re-attached the v19 for a check on the list.
> You are marked as the committer of this patch in the CF app since last
> April and this patch is marked as ready for committer. Are you planning
> to look at it soon?

Here is yet another rebase.

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-20.patch text/x-diff 26.1 KB

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2018-10-02 06:52:20 Re: Commit fest 2018-09
Previous Message Michael Paquier 2018-10-02 06:40:14 Re: [PATCH] Add support for ON UPDATE/DELETE actions on ALTER CONSTRAINT