| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | 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 11:04:21 |
| Message-ID: | 54912a3b-fec1-eb85-4971-46de1a1d0f5e@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On 2020-03-17 16:04, Robert Haas wrote:
>>> (It doesn't seem like we're all that careful about whether we're using
>>> int, which is signed, or Index, which is unsigned, and we might want
>>> to go around and tighten that up.
>>
>> Yeah, I'd be leery of trying to use that last bit. The cost-benefit
>> ratio on that is *definitely* not attractive.
>
> That seems clear, but trying to be consistent about the types we use
> for things is a good idea on general principle, even if we have no
> intention of doing anything that really relies on it any time in the
> forseeable future. If nothing else, it might avoid some compiler
> warnings.
You could make INNER_VAR -1 and so on. Then it would probably break
quite clearly if it's not signedness clean.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Demarest, Jamie | 2020-03-19 12:48:12 | RE: Postgresql create a core while trying log a message to syslog |
| Previous Message | Richard Guo | 2020-03-19 09:28:19 | Re: Optimizer Doesn't Push Down Where Expressions on Rollups |