| From: | Amit Langote <amitlangote09(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | digoal(at)126(dot)com, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: BUG #16302: too many range table entries - when count partition table(65538 childs) |
| Date: | 2020-03-16 02:27:55 |
| Message-ID: | CA+HiwqFZRY=t9jzgbMq5aiKSLWsAj_XhycpULY_PY2W65_cLNw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Sun, Mar 15, 2020 at 12:03 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> PG Bug reporting form <noreply(at)postgresql(dot)org> writes:
> > when i count a partition table with many childs , it's error below:
>
> > postgres=> select count(*) from p;
> > ERROR: 54000: too many range table entries
> > LOCATION: add_rte_to_flat_rtable, setrefs.c:425
>
> This hardly seems like a bug. We do not support an infinite number of
> partitions --- and in the real world, performance would have tanked
> long before you got to this many partitions.
Would it make sense to document this hard upper bound on the number of
relations that can be handled by a query?
--
Thank you,
Amit
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2020-03-16 02:38:30 | Re: BUG #16302: too many range table entries - when count partition table(65538 childs) |
| Previous Message | legrand legrand | 2020-03-15 17:35:55 | pg_stat_statements: rows not updated for CREATE TABLE AS SELECT statements |