Viewing profile — Lockerman
Lockerman
HN member- Joined
- Thu, Oct 31, 2019, 11:00 PM UTC
- HN karma
- 17
- Public activity
- 7 items
- HN profile
- View on Hacker News ↗
About Lockerman
No profile information was provided.
Recent public activity
-
comment
Comment #28935459
Timescale engineer here The initial drive for this was some of the work we did on Promscale, along with some observations I made when experimenting with potential optimizations for…
-
comment
Comment #28922454
Not yet, right now all datapoints must be known at the during the sort
-
comment
Comment #28920229
> Oh or I see timevector returns a custom datatype, so I suppose the answer is it has to be one of a fixed number of provided types? Exactly! These aren't general arithmetic operat…
-
comment
Comment #28920159
(Timescale engineer here) To summarize a bit on what David said here[1]: there are no modifications to the query engine, this is all using Postgres's custom operator support. https…
-
comment
Comment #28528142
a separate implementation
-
comment
Comment #23920605
Timescale engineer here. I'm betting we'll see a nice win; we tend to see write-mostly workloads the UNDO shouldn't be too expensive, and the smaller tuple sizes should be nice. We…
-
comment
Comment #21874904
Hi, Timescale engineer here, do you happen to remember around when/in what version you ran into this bug?