From: | Leonardo Francalanci <m_lists(at)yahoo(dot)it> |
---|---|
To: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Fast insertion indexes: why no developments |
Date: | 2013-10-30 11:23:46 |
Message-ID: | 1383132226.89556.YahooMailNeo@web172603.mail.ir2.yahoo.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> What is the reason for needing such fast access to individual groups
> of records? Sure sounds like the NSA or similar ;-)
Users need to search all calls originated from/to a user or from/to a specific mobile phone to answer/analyze customers' probl... ok, I give up: I work for the NSA ;)
> In terms of generality, do you think its worth a man year of developer
> effort to replicate what you have already achieved? Who would pay?
1) I haven't achieved what I need: realtime indexing. I can't query the "current 15 minutes" table efficiently. Plus, K*log(N) is not that great when you have a lot of K.
2) I'm not suggesting that this is top priority. I'm asking if there's something else, other than "we don't have time for this", that I don't know. In fact, I don't even know if those indexes types would really help in my (specific) case. That's why my original question was "why aren't there developments in this area": I didn't mean to imply someone should do it. I just wanted to know if those indexes were already discussed (and maybe dismissed for some reason) in the past...
From | Date | Subject | |
---|---|---|---|
Next Message | Kaare Rasmussen | 2013-10-30 11:29:40 | Re: Fast insertion indexes: why no developments |
Previous Message | Simon Riggs | 2013-10-30 11:08:02 | Re: Fast insertion indexes: why no developments |