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

From: Andrey Borodin <x4mmm(at)yandex-team(dot)ru>
To: Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru>
Cc: 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-28 19:30:05
Message-ID: 90E36CEA-9E49-4941-A430-3CC42730620E@yandex-team.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> 28 авг. 2018 г., в 14:18, Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru> написал(а):
>
> OK, but I think cube_c_f8() and cube_c_f8_f8() also need to be
> revised. Also, I think this behavior should be covered by regression
> tests.
True. Also there's one case in cube_subset.

Best regards, Andrey Borodin.

Attachment Content-Type Size
cube_check_dim.diff application/octet-stream 11.6 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2018-08-28 19:30:31 Re: More parallel pg_dump bogosities
Previous Message Tom Lane 2018-08-28 19:11:46 Re: More parallel pg_dump bogosities