From: | Josh berkus <josh(at)agliodbs(dot)com> |
---|---|
To: | Bruce Momjian <bruce(at)momjian(dot)us>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi> |
Cc: | Konstantin Knizhnik <k(dot)knizhnik(at)postgrespro(dot)ru>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Academic help for Postgres |
Date: | 2016-05-11 16:58:19 |
Message-ID: | 573364AB.30208@agliodbs.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 05/11/2016 07:54 AM, Bruce Momjian wrote:
> On Wed, May 11, 2016 at 05:41:21PM +0300, Heikki Linnakangas wrote:
>> On 11/05/16 17:32, Bruce Momjian wrote:
>>> On Wed, May 11, 2016 at 05:31:10PM +0300, Konstantin Knizhnik wrote:
>>>> On 11.05.2016 17:20, Bruce Momjian wrote:
>>>>> I am giving a keynote at an IEEE database conference in Helsinki next
>>>>> week (http://icde2016.fi/) (Yes, I am not attending PGCon Ottawa
>>>>> because I accepted the Helsinki conference invitation before the PGCon
>>>>> Ottawa date was changed from June to May).
>>>>>
>>>>> As part of the keynote, I would like to mention areas where academia can
>>>>> help us. The topics I can think of are:
>>>>>
>>>>> Query optimization
>>>>> Optimizer statistics
>>>>> Indexing structures
>>>>> Reducing function call overhead
>>>>> CPU locality
>>>>> Sorting
>>>>> Parallelism
>>>>> Sharding
>>>>>
>>>>> Any others?
>>>>>
>>>> Incremental materialized views?
>>>
>>> I don't know. Is that something academics would research?
>>
>> Absolutely! There are plenty of papers on how to keep materialized views
>> up-to-date.
>
> Oh, OK. I will add it.
>
Together with that, automated substitution of materialized views for
query clauses.
Also: optimizing for new hardware, like persistent memory.
--
--
Josh Berkus
Red Hat OSAS
(any opinions are my own)
From | Date | Subject | |
---|---|---|---|
Next Message | David G. Johnston | 2016-05-11 17:01:46 | Re: Does Type Have = Operator? |
Previous Message | Robert Haas | 2016-05-11 16:54:14 | Re: Does Type Have = Operator? |