Re: seems like a bug in pgbench -R

From: Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>
To: Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: seems like a bug in pgbench -R
Date: 2019-03-16 10:13:58
Message-ID: alpine.DEB.2.21.1903160920380.2506@lancre
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

Hello Tomas,

>>>> So I guess this is a bug in 12788ae49e1933f463bc59a6efe46c4a01701b76, or
>>>> one of the other commits touching this part of the code.
>> I could not reproduce this issue on head, but I confirm on 11.2.
> AFAICS on head it's fixed by 3bac77c48f166b9024a5ead984df73347466ae12

Thanks for the information.

I pinpointed the exact issue in one go: no surprise given that the patch
was motivated by cleaning up this kind of external state machine changes
which I thought doubtful and error prone.

Attached is a fix to apply on pg11.


Attachment Content-Type Size
pg11-pgbench-rate-fix-1.patch text/x-diff 464 bytes

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Magnus Hagander 2019-03-16 10:18:17 Re: Make pg_checksums complain if compiled BLCKSZ and data folder's block size differ
Previous Message Alexander Korotkov 2019-03-16 09:35:52 Re: jsonpath