pg.ddx.io pgsql-students@postgresql.org mailing list archive
help / color / mirror / Atom feedAnother idea for GSoC indexing project
4+ messages / 3 participants
[nested] [flat]
* Another idea for GSoC indexing project
@ 2013-04-24 14:11 Alexander Korotkov <aekorotkov@gmail.com>
2013-04-24 14:38 ` Re: Another idea for GSoC indexing project Бочечко Арсений <slua@ukr.net>
0 siblings, 1 reply; 4+ messages in thread
From: Alexander Korotkov @ 2013-04-24 14:11 UTC (permalink / raw)
To: pgsql-students
Hi, everybody!
The major reason why we have so small number of GiST/SP-GiST/GIN
implementations is that their interface function takes arguments of
"internal" datatype (actually they are mostly pointers, not normal
PostgreSQL datatypes). So, you actually can implement them in C. It
discourages many users.
Idea of project is to provide alternative interfaces for GiST/SP-GiST/GIN
which deal with composite types and arrays. Then users can write
GiST/SP-GiST/GIN implementations on whatever they like SQL, pl/pgSQL,
pl/Python etc.
Probably someone would like to put his hands on it?
------
With best regards,
Alexander Korotkov.
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: Another idea for GSoC indexing project
2013-04-24 14:11 Another idea for GSoC indexing project Alexander Korotkov <aekorotkov@gmail.com>
@ 2013-04-24 14:38 ` Бочечко Арсений <slua@ukr.net>
2013-04-24 15:05 ` Re: Another idea for GSoC indexing project Alexander Korotkov <aekorotkov@gmail.com>
0 siblings, 1 reply; 4+ messages in thread
From: Бочечко Арсений @ 2013-04-24 14:38 UTC (permalink / raw)
To: Alexander Korotkov <aekorotkov@gmail.com>; +Cc: pgsql-students
Sounds interesting, but this will also require a wrapper for this
composite types?
> --- Исходное сообщение ---
От кого: "Alexander Korotkov" <aekorotkov@gmail.com>
Дата: 24 апреля 2013, 17:12:29
Hi, everybody!
The major reason why we have so small number of GiST/SP-GiST/GIN
implementations is that their interface function takes arguments of
"internal" datatype (actually they are mostly pointers, not normal
PostgreSQL datatypes). So, you actually can implement them in C. It
discourages many users.
Idea of project is to provide alternative interfaces for
GiST/SP-GiST/GIN which deal with composite types and arrays. Then
users can write GiST/SP-GiST/GIN implementations on whatever they
like SQL, pl/pgSQL, pl/Python etc.Probably someone would like to put
his hands on it?
------
With best regards,
Alexander Korotkov.
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: Another idea for GSoC indexing project
2013-04-24 14:11 Another idea for GSoC indexing project Alexander Korotkov <aekorotkov@gmail.com>
2013-04-24 14:38 ` Re: Another idea for GSoC indexing project Бочечко Арсений <slua@ukr.net>
@ 2013-04-24 15:05 ` Alexander Korotkov <aekorotkov@gmail.com>
2013-05-01 22:25 ` Re: Another idea for GSoC indexing project Tomas Vondra <tv@fuzzy.cz>
0 siblings, 1 reply; 4+ messages in thread
From: Alexander Korotkov @ 2013-04-24 15:05 UTC (permalink / raw)
To: Бочечко Арсений <slua@ukr.net>; +Cc: pgsql-students
On Wed, Apr 24, 2013 at 6:38 PM, Бочечко Арсений <slua@ukr.net> wrote:
> Sounds interesting, but this will also require a wrapper for this
> composite types?
>
For SQL and PL/pgSQL it's not. I'm not sure about rest of procedural
languages. Should be checked.
------
With best regards,
Alexander Korotkov.
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: Another idea for GSoC indexing project
2013-04-24 14:11 Another idea for GSoC indexing project Alexander Korotkov <aekorotkov@gmail.com>
2013-04-24 14:38 ` Re: Another idea for GSoC indexing project Бочечко Арсений <slua@ukr.net>
2013-04-24 15:05 ` Re: Another idea for GSoC indexing project Alexander Korotkov <aekorotkov@gmail.com>
@ 2013-05-01 22:25 ` Tomas Vondra <tv@fuzzy.cz>
0 siblings, 0 replies; 4+ messages in thread
From: Tomas Vondra @ 2013-05-01 22:25 UTC (permalink / raw)
To: pgsql-students
On 24.4.2013 17:05, Alexander Korotkov wrote:
>
> On Wed, Apr 24, 2013 at 6:38 PM, Бочечко Арсений <slua@ukr.net
> <mailto:slua@ukr.net>> wrote:
>
> Sounds interesting, but this will also require a wrapper for this
> composite types?
>
> For SQL and PL/pgSQL it's not. I'm not sure about rest of procedural
> languages. Should be checked.
This seems like a really neat project idea, however as I have never used
GIN/GiST APIs, I can't really judge the benefits. Could someone prepare
a simple example of a simple composite type and implementation of
GIN/GiST index with the current and new APIs? Not a complete
implementation, just a simple example of how the new API would make it
more simple.
BTW I think the project should include a simple benchmark, comparing the
old C APIs and the new PL APIs.
kind regards
Tomas
--
Sent via pgsql-students mailing list (pgsql-students@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-students
^ permalink raw reply [nested|flat] 4+ messages in thread
end of thread, other threads:[~2013-05-01 22:25 UTC | newest]
Thread overview: 4+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2013-04-24 14:11 Another idea for GSoC indexing project Alexander Korotkov <aekorotkov@gmail.com>
2013-04-24 14:38 ` Бочечко Арсений <slua@ukr.net>
2013-04-24 15:05 ` Alexander Korotkov <aekorotkov@gmail.com>
2013-05-01 22:25 ` Tomas Vondra <tv@fuzzy.cz>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox