genomic locus - Mailing list pgsql-hackers

From Gene Selkov
Subject genomic locus
Date
Msg-id CAMAJB0wsztWZE3wfaHkg63Ug1xMht+wcmf-E3_=ON+oyyGRsXQ@mail.gmail.com
Whole thread Raw
Responses Re: genomic locus  (Michael Paquier <michael.paquier@gmail.com>)
Re: genomic locus  (Robert Haas <robertmhaas@gmail.com>)
Re: genomic locus  (PostgreSQL - Hans-Jürgen Schönig <postgres@cybertec.at>)
Re: genomic locus  (Craig Ringer <craig@2ndquadrant.com>)
Re: genomic locus  (Oleg Bartunov <obartunov@gmail.com>)
List pgsql-hackers
Greetings everyone,

I need a data type to represent genomic positions, which will consist of a string and a pair of integers with interval logic and access methods. Sort of like my seg type, but more straightforward.

I noticed somebody took a good care of seg while I was away for the last 20 years, and I am extremely grateful for that. I have been using it. In the meantime, things have changed and now I am almost clueless about how you deal with contributed modules and what steps I should take once I get it to work. Also, is it a good idea to clone and fix seg for this purpose, or is there a more appropriate template? Or maybe just building it from scratch will be a better idea?

I have seen a lot of bit rot in other extensions (never contributed) that I have not maintained since 2009 and I now I am unable to fix some of them, so I wonder how much of old knowledge is still applicable. In other words, is what I see in new code just a change of macros or the change of principles?

Thanks,

--Gene

pgsql-hackers by date:

Previous
From: Matthew Kelly
Date:
Subject: Bug: Ambiguous Column Reference Allowed When Joining to pg_roles.oid
Next
From: Robert Haas
Date:
Subject: Re: Top-N sorts verses parallelism