Received: from malur.postgresql.org ([2a02:16a8:dc51::56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1fucBN-0002bh-D4 for pgsql-hackers@arkaria.postgresql.org; Tue, 28 Aug 2018 11:29:13 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1fucBL-0000Rj-O9 for pgsql-hackers@arkaria.postgresql.org; Tue, 28 Aug 2018 11:29:11 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1fucBL-0000Rc-HW for pgsql-hackers@lists.postgresql.org; Tue, 28 Aug 2018 11:29:11 +0000 Received: from lungold.riddles.org.uk ([82.68.208.19]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1fucBI-00006d-M9 for pgsql-hackers@postgresql.org; Tue, 28 Aug 2018 11:29:11 +0000 Received: from [192.168.127.1] (port=48830 helo=caithnard.riddles.org.uk) by lungold.riddles.org.uk with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.88 (FreeBSD)) (envelope-from ) id 1fucBG-0008O1-I0 for pgsql-hackers@postgresql.org; Tue, 28 Aug 2018 11:29:06 +0000 Received: from [127.0.0.1] (port=44322 helo=caithnard.riddles.org.uk) by caithnard.riddles.org.uk with esmtp (Exim 4.89 (FreeBSD)) (envelope-from ) id 1fucBF-000BQ7-Mz for pgsql-hackers@postgresql.org; Tue, 28 Aug 2018 11:29:05 +0000 From: Andrew Gierth To: pgsql-hackers@postgresql.org Subject: Dimension limit in contrib/cube (dump/restore hazard?) Message-ID: <87va7uybt4.fsf@news-spur.riddles.org.uk> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.1 (berkeley-unix) Date: Tue, 28 Aug 2018 12:29:04 +0100 MIME-Version: 1.0 Content-Type: text/plain List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk 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)