RE: GSOC 2018 Project - A New Sorting Routine

Thanks for your time! From: Tomas Vondra Sent: August 1, 2018 6:30 AM To: Kefan Yang Cc: Andrey Borodin; Peter Geoghegan; alvhe...@2ndquadrant.com; PostgreSQL Hackers Subject: Re: GSOC 2018 Project - A New Sorting Routine On 07/30/2018 11:21 PM, Kefan Yang wrote: > Hey Tomas! > &

RE: GSOC 2018 Project - A New Sorting Routine

Hey Tomas! Sorry to bother but it would be great if we can get the test results this week. Regards, Kefan From: Tomas Vondra Sent: July 24, 2018 8:16 AM To: Kefan Yang Cc: Andrey Borodin; Peter Geoghegan; alvhe...@2ndquadrant.com; PostgreSQL Hackers Subject: Re: GSOC 2018 Project - A New

Re: GSOC 2018 Project - A New Sorting Routine

On 07/24/2018 12:21 AM, Kefan Yang wrote: Hi Tomas! I did a few tests on my own Linux machine, but the problem is that my resources on AWS(CPU, RAM and even Disk space) are very limited. I considered establishing virtual machine on my own PC but the performance is even worse. My

RE: GSOC 2018 Project - A New Sorting Routine

Subject: Re: GSOC 2018 Project - A New Sorting Routine I don't have any script for that - load the files into a spreadsheet, create pivot tables and you're done. regards On 07/18/2018 11:13 PM, Kefan Yang wrote: > Hey Tomas! > >   > > I am trying to reproduce the results on my mac

Re: GSOC 2018 Project - A New Sorting Routine

bowt.ie>; Kefan Yang > <mailto:starord...@gmail.com>; PostgreSQL Hackers > <mailto:pgsql-hackers@lists.postgresql.org> > *Subject: *Re: GSOC 2018 Project - A New Sorting Routine > >   > >   > >   > > On 07/18/2018 07:06 AM, Andrey Borodin wrote: &g

RE: GSOC 2018 Project - A New Sorting Routine

Hey Tomas! I am trying to reproduce the results on my machine. Could you please share the script to generate .ods files? Regards, Kefan From: Tomas Vondra Sent: July 18, 2018 2:05 AM To: Andrey Borodin Cc: Peter Geoghegan; Kefan Yang; PostgreSQL Hackers Subject: Re: GSOC 2018 Project - A New

Re: GSOC 2018 Project - A New Sorting Routine

Hi, Tomas! > 15 июля 2018 г., в 1:20, Tomas Vondra > написал(а): > > So I doubt it's this, but I've tweaked the scripts to also set this GUC > and restarted the tests on both machines. Let's see what that does. Do you observe any different results? Thanks! Best regards, Andrey Borodin.

Re: GSOC 2018 Project - A New Sorting Routine

On 07/14/2018 12:10 AM, Peter Geoghegan wrote: > On Fri, Jul 13, 2018 at 3:04 PM, Kefan Yang wrote: >> 1. Slow on CREATE INDEX cases. >> >> I am still trying to figure out where the bottleneck is. Is the data pattern >> in index creation very different from other cases? Also, pg_qsort has >>

Re: GSOC 2018 Project - A New Sorting Routine

On Fri, Jul 13, 2018 at 3:04 PM, Kefan Yang wrote: > 1. Slow on CREATE INDEX cases. > > I am still trying to figure out where the bottleneck is. Is the data pattern > in index creation very different from other cases? Also, pg_qsort has > 10%-20% advantage at creating index even on sorted data

Fwd: GSOC 2018 Project - A New Sorting Routine

-- Forwarded message -- From: Kefan Yang Date: 2018-07-13 15:02 GMT-07:00 Subject: Re: GSOC 2018 Project - A New Sorting Routine To: Tomas Vondra Hey Tomas, Thanks for your reply! First I’d like to make some clarification about my test result. > First of all, test

GSOC 2018 Project Progress

Hello Hackers! My name is Kefan Yang, and I am working on my Google Summer of Code 2018 project. For the first evaluation, I should be able to hand in: 1. the benchmark implementations of introsort, timsort, dual-pivot quicksort and radixsort. 2. Phase 1(random array) and 2(worst case) of the

Re: GSoC 2018: thrift encoding format

Thanks guys for your ideas! I feel like it is easier to follow pg_protobuf 's method to design and implement pg_thrift for a postgres beginner like me. I can refer pg_protobuf's way of using functions, writing tests, etc. I will reconsider what's the returned format for list, sets, and struct,

Re: GSoC 2018: thrift encoding format

Greetings, * Aleksander Alekseev (a.aleks...@postgrespro.ru) wrote: > > I understand that you're open to having it as a new data type or as a > > bytea, but I don't agree. This should be a new data type, just as json > > is a distinct data type and so is jsonb. > > Could you please explain in a

Re: GSoC 2018: thrift encoding format

Hello Stephen, > Perhaps the design decisions aren't all made beforehand, but they also > shouldn't be made in a vacuum- there should be discussions on -hackers > about what the right decision is for a given aspect and that's what > should be worked towards. +1, agree. > > Personally I would

Re: GSoC 2018: thrift encoding format

Greetings, * Aleksander Alekseev (a.aleks...@postgrespro.ru) wrote: > >> Personally I think raw data bytes are OK if functions for getting all > >> keys and values from this data are provided > > > > What is the purpose of using Thrift "encoding" if it turns out to be a > > simple wrapper for

Re: GSoC 2018: thrift encoding format

Hello Vladimir, > I'm just trying to figure out what are the use cases for using that Thrift > extension. You can find an answer in the project description: https://wiki.postgresql.org/wiki/GSoC_2018#Thrift_datatype_support_.282018.29 -- Best regards, Aleksander Alekseev signature.asc

Re: GSoC 2018: thrift encoding format

>I mean Charles is free to choose the interface for the extension he believes is right I'm just trying to figure out what are the use cases for using that Thrift extension. For instance, it would be interesting if Thrift was an alternative way to transfer data between client and the database. I

Re: GSoC 2018: thrift encoding format

Hello Vladimir, >> Personally I think raw data bytes are OK if functions for getting all >> keys and values from this data are provided > > What is the purpose of using Thrift "encoding" if it turns out to be a > simple wrapper for existing binary data? > > Do you mean the goal is to have

Re: GSoC 2018: thrift encoding format

>Personally I think raw data bytes are OK if functions for getting all keys and values from this data are provided What is the purpose of using Thrift "encoding" if it turns out to be a simple wrapper for existing binary data? Do you mean the goal is to have "get/set" functions to fetch data out

Re: GSOC 2018

Hi, Joshua! > 2 мая 2018 г., в 22:05, Joshua D. Drake написал(а): > > Who is coordinating GSOC this year? Stephen Frost is org admin. Best regards, Andrey Borodin.

Re: GSoC 2018: thrift encoding format

Hello Charles, > Thanks for your confirm Aleksander! > Also I am thinking of how to deal with complex > data structure like map, list, or set. I guess one possible > solution is to get raw data bytes for these data structure? > Otherwise it could be hard to wrap into a Datum. Personally I think

Re: GSoC 2018: thrift encoding format

Thanks for your confirm Aleksander! Also I am thinking of how to deal with complex data structure like map, list, or set. I guess one possible solution is to get raw data bytes for these data structure? Otherwise it could be hard to wrap into a Datum. 2018-05-02 8:38 GMT-07:00 Aleksander Alekseev

GSOC 2018

-hackers, Who is coordinating GSOC this year? Thanks, JD -- Command Prompt, Inc. || http://the.postgres.company/ || @cmdpromptinc PostgreSQL centered full stack support, consulting and development. Advocate: @amplifypostgres || Learn: https://postgresconf.org * Unless otherwise

Re: GSoC 2018: thrift encoding format

Hello Charles, > Can I assume the data in thrift is always send inside a struct? Sure! > I think this question also valid for protobuf? Right, pg_protobuf assumes that data is always a message which is an equivalent of Thrift's struct. -- Best regards, Aleksander Alekseev signature.asc

GSoC 2018: thrift encoding format

Hi Aleksander, Start to study the format of thrift encoding format (binary protocol) and found this document( https://erikvanoosten.github.io/thrift-missing-specification/#_struct_encoding). Having one question. Can I assume the data in thrift is always send inside a struct? Otherwise, it

RE: GSoC 2018: Sorting Algorithm and Benchmarking

Hey, I’ve joined the workspace. The username is Kefan Yang I agree we can create a channel for this project From: Andrey Borodin Sent: April 27, 2018 9:22 PM To: Kefan Yang Cc: PostgreSQL Hackers; Atri Sharma Subject: Re: GSoC 2018: Sorting Algorithm and Benchmarking > 27 апр. 2018 г., в

Re: GSoC 2018: Sorting Algorithm and Benchmarking

+1 For Slack On Sat, 28 Apr 2018, 09:52 Andrey Borodin, wrote: > > > > 27 апр. 2018 г., в 23:23, Kefan Yang написал(а): > > > > I think Slack would be great for our communication > > Here's Slack invite app http://postgres-slack.herokuapp.com/ >

Re: GSoC 2018: Sorting Algorithm and Benchmarking

> 27 апр. 2018 г., в 23:23, Kefan Yang написал(а): > > I think Slack would be great for our communication Here's Slack invite app http://postgres-slack.herokuapp.com/ Should we create a channel for this project? Best regards, Andrey Borodin.

RE: GSoC 2018: Sorting Algorithm and Benchmarking

Thank you for the feedback! I think Slack would be great for our communication From: Andrey Borodin Sent: April 26, 2018 11:38 PM To: Kefan Yang Cc: PostgreSQL Hackers; Atri Sharma Subject: Re: GSoC 2018: Sorting Algorithm and Benchmarking Hi! > 26 апр. 2018 г., в 0:12, Kefan Yang <s

RE: GSoC 2018: Sorting Algorithm and Benchmarking

Hey, This executable should read a config file (path to sorting routines, test data size etc.), perform tests on different sorting routines, and output the result. Kefan From: Robert Haas Sent: April 26, 2018 11:53 AM To: Kefan Yang Cc: Andrey Borodin; PostgreSQL Hackers Subject: Re: GSoC 2018

Re: GSoC 2018: Sorting Algorithm and Benchmarking

Hi! > 26 апр. 2018 г., в 0:12, Kefan Yang написал(а): > > My name is Kefan Yang. I am so excited that my proposal ‘Sorting Algorithm > and Benchmarking 2018’ has been accepted. Welcome! I'm also glad you've chosen this project. > I see on the Wiki page that you can

Re: GSoC 2018: Sorting Algorithm and Benchmarking

On Wed, Apr 25, 2018 at 3:12 PM, Kefan Yang wrote: > If I understand it correctly, the sorting benchmark should be an executable > under the src/bin/ folder just like pgbench? What would this executable do, exactly? -- Robert Haas EnterpriseDB: http://www.enterprisedb.com

Project Proposal for GSOC 2018

Hello! I have attached the project proposal to develop the PostgreSQL Performance Farm Website for GSOC 2018 with this email. Please review my proposal. Thanks! Regards, Ravindu Perera GSOC 2018 Project Proposal - Performance Farm Web Application.pdf Description: Adobe PDF document

Re: GSOC 2018 Proposal review

, 2018 at 7:34 AM, Mark Wong <m...@2ndquadrant.com> wrote: > Hi Garima, > > On Tue, Mar 20, 2018 at 10:36:05PM +0530, Garima Natani wrote: > > Hi All, > > > > I am looking forward to working with PostgreSQL organization In GSoC > 2018. > > Glad to see you're

Re: GSOC 2018 Proposal review

Hi Garima, On Tue, Mar 20, 2018 at 10:36:05PM +0530, Garima Natani wrote: > Hi All, > > I am looking forward to working with PostgreSQL organization In GSoC 2018. Glad to see you're interested in this project! > I have created Proposal for "Develop Performance Farm Dat

Re: Re: GSOC 2018 Ideas

On Sat, Mar 24, 2018 at 8:39 AM, Vimal Rathod wrote: > > Thank you for replying to my message in very short time. As you have said, I > looked into the url and found that I am interested in doing > TOAST'ing in Slices Project. Can you give me some more details about this

Fwd: Re: GSOC 2018 Ideas

-- Forwarded message -- From: "Vimal Rathod" <vimalrathod...@gmail.com> Date: 23-Mar-2018 9:51 PM Subject: Re: GSOC 2018 Ideas To: "Jaime Soler" <jaime.so...@gmail.com> Cc: Thank you for replying to my message in very short time. As you have said,

Re: GSOC 2018 Ideas

you may have a look at https://wiki.postgresql.org/wiki/GSoC_2018 and tell us if you like some of them 2018-03-23 15:32 GMT+01:00 Vimal Rathod : > Hey there, > > I am Vimal currently pursuing my undergraduate degree in computer science ,I > would love to work with you

GSOC 2018 Ideas

Hey there, I am Vimal currently pursuing my undergraduate degree in computer science ,I would love to work with you via the GSoC program this summer. I wanted to know which all projects I can work on. I have good knowledge in c,java,python,SQL and other web development languages.Can anyone

Re: [GSoC 2018] Proposal Draft

Hi Kefar! > 18 марта 2018 г., в 5:34, Kefan Yang написал(а): > > I am Kefan Yang, a third-year Computing Science student from Simon Fraser > University, Canada. I am very interested in the sorting algorithm > benchmarking and implementation issue you mentioned on the

Re: [GSoC 2018] Proposal Draft

On Sat, Mar 17, 2018 at 7:00 PM, Kefan Yang wrote: > What I am trying to say here is that similar optimizations can be applied to > novel algorithms or other implementations of quicksort. A novel algorithm is something to avoid here, because novel techniques tend to only

Re: [GSoC 2018] Proposal Draft

Thanks for your quick feedback! """ Industrial implementation of selected sorting algorithm: The industrial version is basically an optimization based on the benchmark implementation. I plan to use optimizations like checking if input array is already sorted or applying insertion sort directly

Re: [GSoC 2018] Proposal Draft

On Sat, Mar 17, 2018 at 5:34 PM, Kefan Yang wrote: > I am Kefan Yang, a third-year Computing Science student from Simon Fraser > University, Canada. I am very interested in the sorting algorithm > benchmarking and implementation issue you mentioned on the idealist of >

[GSoC 2018] Proposal Draft

Hi everyone, I am Kefan Yang, a third-year Computing Science student from Simon Fraser University, Canada. I am very interested in the *sorting algorithm benchmarking and implementation* issue you mentioned on the idealist of Google Summer of Code 2018. I am currently working on my proposal, but

Re: GSOC 2018 proposal

Hello Charles, > I am currently preparing a proposal for pg_thrift project. I noticed > that there are several protocols supported by thrift, which ones do we > have higher priority? I mean which ones I need to implement during > this project? Binary protocols, i.e. TBinaryProtocol and

GSOC 2018 proposal

Hi Aleksander, I am currently preparing a proposal for pg_thrift project. I noticed that there are several protocols supported by thrift, which ones do we have higher priority? I mean which ones I need to implement during this project? Thanks, Charles.

Re: GSOC 2018 ideas

2018-03-05 1:42 GMT-08:00 Aleksander Alekseev : > Hello Charles, > > >Went through the documents listed by you, and they are helpful! > > It seems the main purpose of extension pg_protobuf is to parse > > a protobuf struct and return the decoded field. May I ask how

Re: GSOC 2018 ideas

Hello Charles, >Went through the documents listed by you, and they are helpful! > It seems the main purpose of extension pg_protobuf is to parse > a protobuf struct and return the decoded field. May I ask how these kinds > of extensions are used in postgreSQL (or in other words, the scenarios

Re: GSOC 2018 ideas

t; >> > I saw PostgreSQL is selected in GSOC 2018 and pretty interested in the >> > ideas of thrift data types support that proposed by you. So, I want to >> > prepare for a proposal based on this idea. >> >> Glad you are interested in this project! >> >

Re: GSOC 2018 ideas

Got it, Aleksander! Will study these documents carefully! 2018-02-26 4:21 GMT-08:00 Aleksander Alekseev <a.aleks...@postgrespro.ru>: > Hello Charles, > > > I saw PostgreSQL is selected in GSOC 2018 and pretty interested in the > > ideas of thrift data types support tha

Re: GSOC 2018 ideas

Hello Charles, > I saw PostgreSQL is selected in GSOC 2018 and pretty interested in the > ideas of thrift data types support that proposed by you. So, I want to > prepare for a proposal based on this idea. Glad you are interested in this project! > Can I have more detailed informa

GSOC 2018 ideas

Hi Aleksander, This is Yan from Columbia University. I saw PostgreSQL is selected in GSOC 2018 and pretty interested in the ideas of thrift data types support that proposed by you. So, I want to prepare for a proposal based on this idea. Can I have more detailed information of what documents

Re: GSoC 2018 Project Ideas & Mentors - Last Call

Hi! > 18 янв. 2018 г., в 21:59, Stephen Frost <sfr...@snowman.net> написал(а): > > I'll be submitting PostgreSQL as an organization for GSoC 2018 soon and > look forward to having another great PostgreSQL GSoC! I've just checked GSoC website. PostgreSQL is accepted as an organ

Re: GSoC 2018 Project Ideas & Mentors - Last Call

On Mon, Jan 22, 2018 at 7:17 PM, Robert Haas wrote: > On Sun, Jan 21, 2018 at 9:02 AM, Amit Kapila wrote: >> How about adding a project to support Unique capability for the Hash >> Index? > > Hmm, that seems pretty hard. > Yeah, but I think here

Re: GSoC 2018 Project Ideas & Mentors - Last Call

On Sun, Jan 21, 2018 at 9:02 AM, Amit Kapila wrote: > How about adding a project to support Unique capability for the Hash > Index? Hmm, that seems pretty hard. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company

Re: GSoC 2018 Project Ideas & Mentors - Last Call

On Thu, Jan 18, 2018 at 10:29 PM, Stephen Frost <sfr...@snowman.net> wrote: > Greetings! > > I've gone through and cleaned up our GSoC 2018 Wiki page: > > https://wiki.postgresql.org/wiki/GSoC_2018 > > Please review! If you have any last-minute items, please ad

Re: GSoC 2018 Project Ideas & Mentors - Last Call

Stephen Frost wrote: > Greetings! > > I've gone through and cleaned up our GSoC 2018 Wiki page: > > https://wiki.postgresql.org/wiki/GSoC_2018 > > Please review! If you have any last-minute items, please add them! > > We could use some more mentors! I'm staying a

Re: GSoC 2018 Project Ideas & Mentors - Last Call

Greetings, * Atri Sharma (atri.j...@gmail.com) wrote: > I can help with the Sorting project. Great! I've added you as a mentor. Thanks! Stephen signature.asc Description: PGP signature

Re: GSoC 2018 Project Ideas & Mentors - Last Call

I can help with the Sorting project. On Thu, Jan 18, 2018 at 10:29 PM, Stephen Frost <sfr...@snowman.net> wrote: > Greetings! > > I've gone through and cleaned up our GSoC 2018 Wiki page: > > https://wiki.postgresql.org/wiki/GSoC_2018 > > Please review! If you have an

GSoC 2018 Project Ideas & Mentors - Last Call

Greetings! I've gone through and cleaned up our GSoC 2018 Wiki page: https://wiki.postgresql.org/wiki/GSoC_2018 Please review! If you have any last-minute items, please add them! We could use some more mentors! If you would have some time over the summer to help with mentoring a GSoC project

Re: GSoC 2018

Hello everyone! > 5 янв. 2018 г., в 1:36, Stephen Frost написал(а): > > * Stephen Frost (sfr...@snowman.net) wrote: >> The deadline for Mentoring organizations to apply is: January 23. > > We currently only have four (4) projects for 2018 listed on our > projects page here:

Re: GSoC 2018

Hi! On Fri, Jan 5, 2018 at 5:26 AM, Stephen Frost wrote: > * Alexander Korotkov (a.korot...@postgrespro.ru) wrote: > > On Thu, Jan 4, 2018 at 11:36 PM, Stephen Frost > wrote: > > > * Stephen Frost (sfr...@snowman.net) wrote: > > > > The deadline for

Re: GSoC 2018

Hi! On Thu, Jan 4, 2018 at 11:36 PM, Stephen Frost wrote: > Greetings -hackers, > > * Stephen Frost (sfr...@snowman.net) wrote: > > The deadline for Mentoring organizations to apply is: January 23. > > We currently only have four (4) projects for 2018 listed on our >

Re: GSoC 2018

Hi, Stefan! > 15 дек. 2017 г., в 15:03, Stefan Keller написал(а): > > What about adding "Learned Index" as project task [*]? > This type of index looks promising for certain properties. > > [*] "The Case for Learned Index Structures" Kraska et al. (Dec 2017) >

Re: GSoC 2018

On Mon, Dec 18, 2017 at 10:53 AM, Aleksander Alekseev wrote: > Hello hackers, > > Thanks you a lot for your feedback. I modified the project description > to make it more clear that it implies augmenting an existing HA > solution, particularly Stolon, and doesn't imply

Re: GSoC 2018

Aleksander, * Aleksander Alekseev (a.aleks...@postgrespro.ru) wrote: > Thanks you a lot for your feedback. I modified the project description > to make it more clear that it implies augmenting an existing HA > solution, particularly Stolon, and doesn't imply solving existing > limitations of

Re: GSoC 2018

Hello hackers, Thanks you a lot for your feedback. I modified the project description to make it more clear that it implies augmenting an existing HA solution, particularly Stolon, and doesn't imply solving existing limitations of logical replication like lack of DDL replication. Removing some

Re: GSoC 2018

On 15/12/17 13:57, Aleksander Alekseev wrote: Hi Stephen, HA/fail-over is a very broad topic, with a lot of pieces that need to be done such that I'm not sure it's really viable, but perhaps a precursor project (synchronous logical replication seems like a prereq, no?) would make more sense.

Re: GSoC 2018

Alex, * Alex Kliukin (al...@hintbits.com) wrote: > On Fri, Dec 15, 2017, at 14:52, Aleksander Alekseev wrote: > > Completely agree, this project can be an improvement for Stolon (or > > Patroni, but I personally never tested or used it, also I got a feeling > > that Google guys will prefer a

Re: GSoC 2018

On Fri, Dec 15, 2017, at 14:52, Aleksander Alekseev wrote: > Completely agree, this project can be an improvement for Stolon (or > Patroni, but I personally never tested or used it, also I got a feeling > that Google guys will prefer a project that is written in Go). This > would make much more

Re: GSoC 2018

Alex, * Alex Kliukin (al...@hintbits.com) wrote: > On Fri, Dec 15, 2017, at 14:30, Stephen Frost wrote: > > * Aleksander Alekseev (a.aleks...@postgrespro.ru) wrote: > > > > > Regarding the difficulty of the project - in fact it's not that > > > difficult. Particularly this project can rely on

Re: GSoC 2018

Hello, On Fri, Dec 15, 2017, at 14:30, Stephen Frost wrote: > Aleksander, > > * Aleksander Alekseev (a.aleks...@postgrespro.ru) wrote: > > > Regarding the difficulty of the project - in fact it's not that > > difficult. Particularly this project can rely on external tools, e.g. > > use Consul

Re: GSoC 2018

Aleksander Alekseev writes: > Hi Stephen, > >> synchronous_commit isn't the same as synchronous_standby_names ... > > What about synchronous_standby_names? Logical replication ignores it and > doesn't wait for ack's from replicas or something? It actually works, see

Re: GSoC 2018

Hi Stephen, > synchronous_commit isn't the same as synchronous_standby_names ... What about synchronous_standby_names? Logical replication ignores it and doesn't wait for ack's from replicas or something? > What might be interesting is seeing if Logical Replication could be > added to Patroni

Re: GSoC 2018

Aleksander, * Aleksander Alekseev (a.aleks...@postgrespro.ru) wrote: > > HA/fail-over is a very broad topic, with a lot of pieces that need to be > > done such that I'm not sure it's really viable, but perhaps a precursor > > project (synchronous logical replication seems like a prereq, no?)

Re: GSoC 2018

Hi Stephen, > HA/fail-over is a very broad topic, with a lot of pieces that need to be > done such that I'm not sure it's really viable, but perhaps a precursor > project (synchronous logical replication seems like a prereq, no?) would > make more sense. Or, perhaps, a different piece of the HA

Re: GSoC 2018

Aleksander, * Aleksander Alekseev (a.aleks...@postgrespro.ru) wrote: > > New entries are certainly welcome and encouraged, just be sure to note > > them as '2018' when you add it. > > I proposed a few ideas: Thanks! > * High availability / failover based on logical replication > * Thrift

Re: GSoC 2018

Stefan, * Stefan Keller (sfkel...@gmail.com) wrote: > 2017-12-15 4:14 GMT+01:00 Stephen Frost : > > Unsurprisingly, we'll need to have an Ideas page again, so I've gone > > ahead and created one (copying last year's): > > What about adding "Learned Index" as project task [*]?

Re: GSoC 2018

Hi! > 15 дек. 2017 г., в 15:03, Stefan Keller написал(а): > What about adding "Learned Index" as project task [*]? > This type of index looks promising for certain properties. I have no high expectation from this idea. But feel that it is necessary at least to validate the

Re: GSoC 2018

Hi, 2017-12-15 4:14 GMT+01:00 Stephen Frost : > Unsurprisingly, we'll need to have an Ideas page again, so I've gone > ahead and created one (copying last year's): What about adding "Learned Index" as project task [*]? This type of index looks promising for certain

Re: GSoC 2018

Hi Stephen, > New entries are certainly welcome and encouraged, just be sure to note > them as '2018' when you add it. I proposed a few ideas: * High availability / failover based on logical replication * Thrift datatype support Hope these ideas are good enough for GSoC. -- Best regards,

GSoC 2018

Greetings -hackers, Google Summer of Code 2018 was announced back in September and they've changed up the timeline a bit [1]. Specifically, they moved up the dates for things like the mentoring organization application deadline, so it's time to start working on our Idea's page for 2018 in