Re: Keep elog(ERROR) and ereport(ERROR) calls in the cold path

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: David Rowley <dgrowleyml(at)gmail(dot)com>
Cc: Andres Freund <andres(at)anarazel(dot)de>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Keep elog(ERROR) and ereport(ERROR) calls in the cold path
Date: 2020-08-03 07:54:06
Message-ID: 20200803075406.GP3317@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Jun 29, 2020 at 09:36:56PM +1200, David Rowley wrote:
> I've attached a graph showing the results for the AMD and Intel runs
> and also csv files of the pgbench tps output. I've also attached each
> version of the patch I tested.
>
> It would be good to see some testing done on other hardware.

Worth noting that the patch set fails to apply. I have moved this
entry to the next CF, waiting on author.
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2020-08-03 07:55:58 Re: SQL/JSON: JSON_TABLE
Previous Message Amit Langote 2020-08-03 07:39:11 Re: problem with RETURNING and update row movement