| From: | Devrim Gündüz <devrim(at)gunduz(dot)org> |
|---|---|
| To: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | CUBE_MAX_DIM |
| Date: | 2020-06-25 10:00:55 |
| Message-ID: | 292ec48bd39b4c61cf12060956a7454dcbbea2d3.camel@gunduz.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
Someone contacted me about increasing CUBE_MAX_DIM
in contrib/cube/cubedata.h (in the community RPMs). The current value
is 100 with the following comment:
* This limit is pretty arbitrary, but don't make it so large that you
* risk overflow in sizing calculations.
They said they use 500, and never had a problem. I never added such patches to the RPMS, and will not -- but wanted to ask if we can safely increase it in upstream?
Regards,
--
Devrim Gündüz
Open Source Solution Architect, Red Hat Certified Engineer
Twitter: @DevrimGunduz , @DevrimGunduzTR
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2020-06-25 10:20:27 | Re: min_safe_lsn column in pg_replication_slots view |
| Previous Message | Daniel Gustafsson | 2020-06-25 09:43:00 | Re: Online checksums patch - once again |