Re: pgbench - add \aset to store results of a combined query
Fabien COELHO <coelho@cri.ensmp.fr>
From: Fabien COELHO <coelho@cri.ensmp.fr>
To: Michael Paquier <michael@paquier.xyz>
Cc: Ibrar Ahmed <ibrar.ahmad@gmail.com>,
PostgreSQL Developers <pgsql-hackers@lists.postgresql.org>
Date: 2020-04-03T05:23:59Z
Lists: pgsql-hackers
Bonjour Michaël, >> Sure. I meant that the feature would make sense to write benchmark scripts >> which would use aset and be able to act on the success or not of this aset, >> not to resurrect it for a hidden coverage test. > > This could always be discussed for v14. We'll see. Or v15, or never, who knows? :-) The use case I have in mind for such a feature is to be able to have a flow of DELETE transactions in a multi-script benchmark without breaking concurrent SELECT/UPDATE transactions. For that, the ability of extracting data easily and testing whether it was non empty would help. > Applied, then. Thanks! Thanks to you! -- Fabien.
Commits
-
Add support for \aset in pgbench
- 9d8ef98800bd 13.0 landed