Re: BUG #16673: Stack depth limit exceeded error while running sysbench TPC-C

From: David Geier <david(at)swarm64(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org, Norman Heino <norman(dot)heino(at)swarm64(dot)com>, Luis Carril <luis(dot)carril(at)swarm64(dot)com>
Subject: Re: BUG #16673: Stack depth limit exceeded error while running sysbench TPC-C
Date: 2020-10-22 06:30:52
Message-ID: 9925f96b-1a9d-a6a9-648f-eda64a66688e@swarm64.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

We re-tested and the bug is gone with PG 13.

Thanks for back patching. Much appreciated.

Best
David

On 19.10.20 16:31, Tom Lane wrote:
> David Geier <david(at)swarm64(dot)com> writes:
>> Thanks for the quick reply. We gonna try it with PSQL 13 and let you
>> know if the bug still appears.
> FYI, I did back-patch, so that fix will be in next month's
> minor releases.
>
> regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message PG Bug reporting form 2020-10-22 07:14:06 BUG #16682: The pg_user_mapping table saves the plaintext password
Previous Message Andrey Borodin 2020-10-22 05:50:48 Re: BUG #16329: Valgrind detects an invalid read when building a gist index with buffering