Re: Dimension limit in contrib/cube (dump/restore hazard?)

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru>
Cc: Andrey Borodin <x4mmm(at)yandex-team(dot)ru>, Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Dimension limit in contrib/cube (dump/restore hazard?)
Date: 2018-08-31 15:18:30
Message-ID: 20180831151830.fqxl6dgrdf2ulsl5@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2018-Aug-30, Alexander Korotkov wrote:

> Personally I get tired with cube.out
> and cube_2.out. They are different with only few checks involving
> scientific notation. But all the patches touching cube regression
> tests should update both cube.out and cube_2.out. I propose to split
> scientific notation checks into separate test.

Good idea.

--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2018-08-31 15:20:01 Re: TupleTableSlot abstraction
Previous Message Andres Freund 2018-08-31 15:15:24 Re: remove ancient pre-dlopen dynloader code