Re: BUG #16302: too many range table entries - when count partition table(65538 childs)

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Amit Langote <amitlangote09(at)gmail(dot)com>, 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-19 13:33:36
Message-ID: 3515.1584624816@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> writes:
> You could make INNER_VAR -1 and so on. Then it would probably break
> quite clearly if it's not signedness clean.

I kinda like this, because it'd avoid having random large constants
in the code.

We'd have to change Var.varno and some other places from Index to
plain int, or else invent a typedef --- but the number of places
currently using plain int for this sort of purpose is very large,
so probably a new typedef is not worth the hassle.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Raschkowski, Michael 2020-03-19 16:44:59 Trigger does not work after partitioning
Previous Message Pavel Suderevsky 2020-03-19 13:22:16 Re: Don't try fetching future segment of a TLI.