Received: from malur.postgresql.org ([2a02:16a8:dc51::56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1fqcue-0007x0-9j for pgsql-hackers@arkaria.postgresql.org; Fri, 17 Aug 2018 11:27:29 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1fqcuc-0000f8-PJ for pgsql-hackers@arkaria.postgresql.org; Fri, 17 Aug 2018 11:27:26 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1fqcuc-0000f1-75 for pgsql-hackers@lists.postgresql.org; Fri, 17 Aug 2018 11:27:26 +0000 Received: from mail.postgrespro.ru ([93.174.131.138]) by makus.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1fqcuY-0003Te-B8 for pgsql-hackers@postgresql.org; Fri, 17 Aug 2018 11:27:24 +0000 Received: from localhost (localhost [127.0.0.1]) by mail.postgrespro.ru (Postfix) with ESMTP id 834E221C29B8; Fri, 17 Aug 2018 14:27:19 +0300 (MSK) X-Virus-Scanned: Debian amavisd-new at postgrespro.ru X-Spam-Flag: NO X-Spam-Score: 0 X-Spam-Level: X-Spam-Status: No, score=x tagged_above=-99 required=4 WHITELISTED tests=[] autolearn=unavailable Received: from mail.postgrespro.ru (cyclops.l.postgrespro.ru [192.168.27.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mail.postgrespro.ru (Postfix) with ESMTPSA id 5050321C29B6; Fri, 17 Aug 2018 14:27:19 +0300 (MSK) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=postgrespro.ru; s=mail; t=1534505239; bh=8MeLdKNUF+C8KOe/x1tgK/eZhYWeNZBHhmG9k5zgwa0=; h=Date:From:To:Cc:Subject:In-Reply-To:References; b=MC0703bUs2ZlZnkSEb6XGC4txhnAdzOrtPDEOZF8QB0FzFD1FFVY9LuGAUCStZ0Ab DaawScmEaRE4KimXSlK6e8ujEocKqpTBADURCkRSaeKElk1R/hsiClCUfHGBNZWg1G cvCVWinD37goIqsLnCLs/+YHKnGR5V4LCC/oe2vo= MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Fri, 17 Aug 2018 14:27:19 +0300 From: Marina Polyakova To: Fabien COELHO Cc: pgsql-hackers@postgresql.org, Alvaro Herrera , Ildus Kurbangaliev , Teodor Sigaev Subject: Re: [HACKERS] WIP Patch: Pgbench Serialization and deadlock errors Organization: Postgres Professional In-Reply-To: References: <20180508193621.dphlgwrd5yz67o2z@alvherre.pgsql> <0569c5309cf536a839e2a3a1433bd113@postgrespro.ru> <976a25a46420c93866ada4051976b1be@postgrespro.ru> <25d7b1f518c218a8c335bdfc6c858ea1@postgrespro.ru> <92869f967d690848c456ac44b371482c@postgrespro.ru> <48b325aa26bb51381a21b27b1553878d@postgrespro.ru> Message-ID: X-Sender: m.polyakova@postgrespro.ru User-Agent: Roundcube Webmail/1.2.4 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On 17-08-2018 14:04, Fabien COELHO wrote: > ... >> Or perhaps we can use a more detailed failure status so for each type >> of failure we always know the command name (argument "cmd") and >> whether the client is aborted. Something like this (but in comparison >> with the first variant ISTM overly complicated): > > I agree., I do not think that it would be useful given that the same > thing is done on all meta-command error cases in the end. Ok! -- Marina Polyakova Postgres Professional: http://www.postgrespro.com The Russian Postgres Company