From: Andrew Gierth <andrew@tao11.riddles.org.uk>
To: pgsql-hackers@postgresql.org
Subject: Dimension limit in contrib/cube (dump/restore hazard?)
Date: Tue, 28 Aug 2018 12:29:04 +0100
Message-ID: <87va7uybt4.fsf@news-spur.riddles.org.uk> (raw)
contrib/cube has an arbitrary limit of 100 on the number of dimensions
in a cube, but it actually enforces that only in cube_in and
cube_enlarge, with the other cube creation functions happy to create
cubes of more dimensions.
I haven't actually tested, but this implies that one can create cubes
that will break dump/restore.
Should this limit be kept, and if so what should it be? (There's
obviously a limit on the size of indexable cubes)
(Noticed because an irc user was trying to use cubes with 512
dimensions with partial success)
--
Andrew (irc:RhodiumToad)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: andrew@tao11.riddles.org.uk
Subject: Re: Dimension limit in contrib/cube (dump/restore hazard?)
In-Reply-To: <87va7uybt4.fsf@news-spur.riddles.org.uk>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox