{"action":"opened","issue":{"url":"https://api.github.com/repos/timescale/timescaledb/issues/277","repository_url":"https://api.github.com/repos/timescale/timescaledb","labels_url":"https://api.github.com/repos/timescale/timescaledb/issues/277/labels{/name}","comments_url":"https://api.github.com/repos/timescale/timescaledb/issues/277/comments","events_url":"https://api.github.com/repos/timescale/timescaledb/issues/277/events","html_url":"https://github.com/timescale/timescaledb/issues/277","id":268576732,"number":277,"title":"Support `tsrange` and similar time data","user":{"login":"Kheldar","id":145132,"avatar_url":"https://avatars3.githubusercontent.com/u/145132?v=4","gravatar_id":"","url":"https://api.github.com/users/Kheldar","html_url":"https://github.com/Kheldar","followers_url":"https://api.github.com/users/Kheldar/followers","following_url":"https://api.github.com/users/Kheldar/following{/other_user}","gists_url":"https://api.github.com/users/Kheldar/gists{/gist_id}","starred_url":"https://api.github.com/users/Kheldar/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Kheldar/subscriptions","organizations_url":"https://api.github.com/users/Kheldar/orgs","repos_url":"https://api.github.com/users/Kheldar/repos","events_url":"https://api.github.com/users/Kheldar/events{/privacy}","received_events_url":"https://api.github.com/users/Kheldar/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2017-10-25T22:53:39Z","updated_at":"2017-10-25T22:53:39Z","closed_at":null,"author_association":"NONE","body":"I have a use case where the main time column for my data is a `tsrange` - each row has a period during which it's active. \r\n\r\nThe main set of queries I need to run on this all centre around \"give me all the rows that were active during <time-period>\" (i.e. they use the `&&`, `@>` and `<@` operators).\r\n\r\nIt'd be awesome if you supported partitioning on ranges, as a GIST index alone in Postgres don't give me the performance I need for the data-sizes I'm dealing with."}}
{"actor":{"display_login":"Kheldar"}}