Re: pgbench - add \aset to store results of a combined query

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Ibrar Ahmed <ibrar(dot)ahmad(at)gmail(dot)com>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org, Fabien Coelho <postgresql(dot)org(at)coelho(dot)net>
Subject: Re: pgbench - add \aset to store results of a combined query
Date: 2019-11-29 05:56:07
Message-ID: 20191129055607.GG2505@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Aug 15, 2019 at 06:30:13PM +0000, Ibrar Ahmed wrote:
> The following review has been posted through the commitfest application:
> make installcheck-world: tested, passed
> Implements feature: tested, passed
> Spec compliant: tested, passed
> Documentation: not tested
>
> The patch passed my review, I have not reviewed the documentation changes.
>
> The new status of this patch is: Ready for Committer

@@ -524,6 +526,7 @@ typedef struct Command
int argc;
char *argv[MAX_ARGS];
char *varprefix;
+ bool aset;

It seems to me that there is no point to have the variable aset in
Command because this structure includes already MetaCommand, so the
information is duplicated. And I would suggest to change
readCommandResponse() to use a MetaCommand in argument. Perhaps I am
missing something?
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2019-11-29 06:01:46 Re: [PATCH] Incremental sort (was: PoC: Partial sort)
Previous Message Andrew Gierth 2019-11-29 05:39:57 A rather hackish POC for alternative implementation of WITH TIES