Re: [HACKERS] GSoC 2017 - Mailing list pgsql-hackers

From Jim Nasby
Subject Re: [HACKERS] GSoC 2017
Date
Msg-id 0353e30e-3254-6ec4-a832-9ca3215b00b2@BlueTreble.com
Whole thread Raw
In response to Re: [HACKERS] GSoC 2017  (Peter van Hardenberg <pvh@pvh.ca>)
Responses Re: [HACKERS] GSoC 2017
List pgsql-hackers
On 1/13/17 3:09 PM, Peter van Hardenberg wrote:
> A new data type, and/or a new index type could both be nicely scoped
> bits of work.

Did you have any particular data/index types in mind?

Personally I'd love something that worked like a python dictionary, but 
I'm not sure how that'd work without essentially supporting a variant 
data type. I've got code for a variant type[1], and I don't think 
there's any holes in it, but the casting semantics are rather ugly. IIRC 
that problem appeared to be solvable if there was a hook in the current 
casting code right before Postgres threw in the towel and said a cast 
was impossible.

1: https://github.com/BlueTreble/variant/
-- 
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
855-TREBLE2 (855-873-2532)



pgsql-hackers by date:

Previous
From: Jim Nasby
Date:
Subject: Re: [HACKERS] GSoC 2017
Next
From: Tomas Vondra
Date:
Subject: Re: [HACKERS] PoC: Grouped base relation