| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Arseny Sher <a(dot)sher(at)postgrespro(dot)ru>, "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Indexes on partitioned tables and foreign partitions |
| Date: | 2018-05-09 15:15:09 |
| Message-ID: | CA+TgmoaHbg3v58KfLiZjzKb5Ufcr0TQsdn37j3wtSnqiWSyZvg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, May 9, 2018 at 11:14 AM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
> On 9 May 2018 at 16:10, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> Robert Haas <robertmhaas(at)gmail(dot)com> writes:
>>> On Wed, May 9, 2018 at 9:08 AM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
>>>> Shouldn't the fix be to allow creation of indexes on foreign tables?
>>>> (Maybe they would be virtual or foreign indexes??)
>>
>>> It might be useful to invent the concept of a foreign index, but not
>>> for v11 a month after feature freeze.
>>
>> Yeah. That's a can of worms we can *not* open at this stage.
>
> Lucky nobody suggested that then, eh? Robert's just making a joke.
Someone did suggest that. It was you.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2018-05-09 15:18:10 | Re: [HACKERS] Cutting initdb's runtime (Perl question embedded) |
| Previous Message | Simon Riggs | 2018-05-09 15:14:30 | Re: Indexes on partitioned tables and foreign partitions |