From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: RelOptInfo -> Relation |
Date: | 2018-02-06 20:11:12 |
Message-ID: | CA+TgmoZT1B4NaM13ZY-qBj4pvi0tV_7cuttrGg8-ghoZRXvx_Q@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Feb 6, 2018 at 2:23 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> If we're going to have to change this at some point (and I bet we
>> are), I'd rather do it before people jam even more stuff into the
>> current system rather than wait until it gets totally out of hand.
>
> While I'm prepared to believe that this *could* be a problem, I repeat
> that you've offered no hard evidence that it actually *is* a problem,
> or might become one in the future. We could easily expend a significant
> amount of effort here for no real return.
Sure. The point of the email was to ask whether there was some
consideration of which I had not thought which makes this utterly
unthinkable; the answer at least so far seems to be "no".
I think it will be interesting to see what happens with the faster
partition pruning patch. If it doesn't run into a problem with this,
then there's no urgent need to do anything here.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2018-02-06 20:16:59 | Re: Add more information_schema columns |
Previous Message | Andres Freund | 2018-02-06 20:02:05 | Why does load_external_function() return PGFunction? |