genomic locus

From: Gene Selkov <selkovjr(at)gmail(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Subject: genomic locus
Date: 2017-12-15 19:49:11
Message-ID: CAMAJB0wsztWZE3wfaHkg63Ug1xMht+wcmf-E3_=ON+oyyGRsXQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2017-12-15 20:13:20 Re: Top-N sorts verses parallelism
Previous Message Matthew Kelly 2017-12-15 19:47:32 Bug: Ambiguous Column Reference Allowed When Joining to pg_roles.oid