| From: | Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Dimension limit in contrib/cube (dump/restore hazard?) |
| Date: | 2018-08-28 11:29:04 |
| Message-ID: | 87va7uybt4.fsf@news-spur.riddles.org.uk |
| Views: | Whole Thread |Raw Message |Download mbox |Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Surafel Temesgen | 2018-08-28 12:14:43 | Re: FETCH FIRST clause PERCENT option |
| Previous Message | Kyotaro HORIGUCHI | 2018-08-28 10:34:36 | Re: Problem while setting the fpw with SIGHUP |