Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dW26W-00026x-3k for pgsql-hackers@arkaria.postgresql.org; Fri, 14 Jul 2017 15:02:04 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1dW26V-0005Mn-JN for pgsql-hackers@arkaria.postgresql.org; Fri, 14 Jul 2017 15:02:03 +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.84_2) (envelope-from ) id 1dW26V-0005Me-1y for pgsql-hackers@postgresql.org; Fri, 14 Jul 2017 15:02:03 +0000 Received: from mail.postgrespro.ru ([93.174.131.138]) by makus.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dW26R-0001rn-Oh for pgsql-hackers@postgresql.org; Fri, 14 Jul 2017 15:02:01 +0000 Received: from localhost (localhost [127.0.0.1]) by mail.postgrespro.ru (Postfix) with ESMTP id 0347421C03F6; Fri, 14 Jul 2017 18:01:57 +0300 (MSK) X-Virus-Scanned: Debian amavisd-new at postgrespro.ru MIME-Version: 1.0 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=postgrespro.ru; s=mail; t=1500044516; bh=l2AjruCeaEMc4nCUKAbP27FZnrmjQhRqCJ+FwNYH8mc=; h=Date:From:To:Cc:Subject:In-Reply-To:References; b=GewkSP112cF7FOPUI6e5Kdk4/JXS4Z2mfAKEFtpf8RdOhglHGzExjlO7w9e9MZDzR G2kBxOhwBB9x9QpRtVNypTJVdFY4gaUM6/sj/TD6vcvqxJp3jeomy3oIVa6Sv9FBDF +Q60O8qcodoyM5GUWAvwLNlElxpI2apS8DxNxaKg= Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Fri, 14 Jul 2017 18:01:56 +0300 From: Marina Polyakova To: Fabien COELHO Cc: PostgreSQL Developers , Kevin Grittner , Andres Freund , Alvaro Herrera , Thomas Munro , Robert Haas Subject: Re: WIP Patch: Pgbench Serialization and deadlock errors Organization: Postgres Professional In-Reply-To: References: <72a0d590d6ba06f242d75c2e641820ec@postgrespro.ru> <6b4a7fb36c9956595a89a08e5368a9c5@postgrespro.ru> <01df6ca86c78e2c80b4e4d021c99d53a@postgrespro.ru> <6ce8613f061001105654673506348c13@postgrespro.ru> <0e7afb8c40e9241510947332be8e2ed2@postgrespro.ru> Message-ID: <5c9f781b61d2292fcbe16ab4ff51499a@postgrespro.ru> X-Sender: m.polyakova@postgrespro.ru User-Agent: Roundcube Webmail/1.2.4 List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-hackers Precedence: bulk Sender: pgsql-hackers-owner@postgresql.org > Well, the short version may be to only do a full transaction retry and > to document that for now savepoints are not handled, and to let that > for future work if need arises. I agree with you. > For progress the output must be short and readable, and probably we do > not care about whether retries came from this or that, so I would let > that out. > > For log and aggregated log possibly that would make more sense, but it > must stay easy to parse. Ok! -- Marina Polyakova Postgres Professional: http://www.postgrespro.com The Russian Postgres Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers