On 2016/06/13 15:52, Michael Paquier wrote:
On Mon, Jun 13, 2016 at 2:42 PM, Tatsuro Yamada
<yamada.tats...@lab.ntt.co.jp> wrote:
I got mistake to write an e-mail to -hackers on last week. :-<
I should have written this.
The bug has not fixed by Tom Lane's patch: commit aeb9ae6.
Because I got the same error using tpc-h.
This looks like a different regression..
I understand it now, thanks. :-)
I checked the list, but the bug is not listed.
https://wiki.postgresql.org/wiki/PostgreSQL_9.6_Open_Items
And the winner is:
04ae11f62e643e07c411c4935ea6af46cb112aa9 is the first bad commit
commit 04ae11f62e643e07c411c4935ea6af46cb112aa9
Author: Robert Haas <rh...@postgresql.org>
Date: Fri Jun 3 14:27:33 2016 -0400
I am adding that to the list of open items.
Oh...
I'll try to run tpc-h if I got a new patch which fixes the bug. :)
Thanks,
Tatsuro Yamada
NTT OSS Center
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
