pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Nathan Boley <npboley@gmail.com>
To: pgsql-performance@postgresql.org
Subject: Re: plpgsql arrays
Date: Fri, 3 Apr 2009 12:03:43 -0700
Message-ID: <6fa3b6e20904031203m3867d02cnbc599c14b123d961@mail.gmail.com> (raw)
In-Reply-To: <1138.1238770111@sss.pgh.pa.us>
References: <alpine.DEB.2.00.0904031420470.21772@aragorn.flymine.org>
	<603c8f070904030647u1c92e13ew53612ac0011ed7c1@mail.gmail.com>
	<alpine.DEB.2.00.0904031455210.21772@aragorn.flymine.org>
	<28595.1238767442@sss.pgh.pa.us>
	<alpine.DEB.2.00.0904031507000.21772@aragorn.flymine.org>
	<29730.1238768681@sss.pgh.pa.us>
	<alpine.DEB.2.00.0904031526080.21772@aragorn.flymine.org>
	<1138.1238770111@sss.pgh.pa.us>

> Uh, no, it wouldn't.  Visually:
>
>        L1      -------------------------
>        L2      -----------
>        L3      ---------------------
>
>        R1                     --------
>
> At L2, you'd conclude that you're done matching R1.
>

No, you should conclude that you're done matching L2. You conclude
you're done matching R1 when you reach L4  ( or there exists a j st
Lj.start > R1.end, or equivalently Lj is strictly greater than R1 )

FWIW, this is a very common problem in bioinformatics. I've mostly
implemented this in python and C. The code is available at
encodestatistics.org. Look in encode.py at the overlap method of the
feature_region class, or ( for the C version ) region_overlap in
block_bootstrap.c ( svn is more up to date for the C ).

-Nathan



view thread (32+ messages)  latest in thread

Message-ID: <6fa3b6e20904031203m3867d02cnbc599c14b123d961@mail.gmail.com>
Permalink:  ../6fa3b6e20904031203m3867d02cnbc599c14b123d961@mail.gmail.com/
Also on:    postgresql.org/message-id/6fa3b6e20904031203m3867d02cnbc599c14b123d961@mail.gmail.com

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: npboley@gmail.com
  Subject: Re: plpgsql arrays
  In-Reply-To: <6fa3b6e20904031203m3867d02cnbc599c14b123d961@mail.gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

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