pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Fabien COELHO <coelho@cri.ensmp.fr>
To: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: Marina Polyakova <m.polyakova@postgrespro.ru>
Cc: pgsql-hackers@postgresql.org, Ildus Kurbangaliev <i.kurbangaliev@postgrespro.ru>
Cc: Teodor Sigaev <teodor@sigaev.ru>
Subject: Re: [HACKERS] WIP Patch: Pgbench Serialization and deadlock errors
Date: Mon, 19 Nov 2018 20:54:49 +0100 (CET)
Message-ID: <alpine.DEB.2.21.1811192044240.4640@lancre> (raw)
In-Reply-To: <20181119160124.7ygg523m3qcb7wii@alvherre.pgsql>
References: <20181119160124.7ygg523m3qcb7wii@alvherre.pgsql>


Hello Alvaro,

> I also think that the pgbench_error() patch should go in before the main
> one.  It seems a bit pointless to introduce code using a bad API only to
> fix the API together with all the new callers immediately afterwards.

I'm not that keen on this part of the patch, because ISTM that introduces 
significant and possibly costly malloc/free cycles when handling error, 
which do not currently exist in pgbench.

Previously an error was basically the end of the script, but with the 
feature being introduced by Marina some errors are handled, in which case 
we end up with paying these costs in the test loop. Also, refactoring 
error handling is not necessary for the new feature. That is why I advised 
to move it away and possibly keep it for later.

Related to Marina patch (triggered by reviewing the patches), I have 
submitted a refactoring patch which aims at cleaning up the internal state 
machine, so that additions and checking that all is well is simpler.

 	https://commitfest.postgresql.org/20/1754/

It has been reviewed, I think I answered to the reviewer concerns, but the 
reviewer did not update the patch state on the cf app, so I do not know 
whether he is unsatisfied or if it was just forgotten.

-- 
Fabien.




view thread (137+ messages)  latest in thread

Message-ID: <alpine.DEB.2.21.1811192044240.4640@lancre>
Permalink:  ../alpine.DEB.2.21.1811192044240.4640@lancre/
Also on:    postgresql.org/message-id/alpine.DEB.2.21.1811192044240.4640@lancre

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: coelho@cri.ensmp.fr, alvherre@2ndquadrant.com, m.polyakova@postgrespro.ru, i.kurbangaliev@postgrespro.ru, teodor@sigaev.ru
  Subject: Re: [HACKERS] WIP Patch: Pgbench Serialization and deadlock errors
  In-Reply-To: <alpine.DEB.2.21.1811192044240.4640@lancre>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox