James Sewell

Hello @lyncodes! Could you please provide some raw data which triggers this issue? I had a play but can't seem to produce your output. One possible reason could be that...

Just adding a live link [https://dbfiddle.uk/L4WfMlIK](https://dbfiddle.uk/L4WfMlIK)

This is great. I'd love to work together to get the helm chart into your stack (I run Developer Advocacy @ Timescale)

Just popping up again to offer help from the Timescale side if needed

shared_buffers are 100% for holding large amounts of data (if that's what you want to do) . Interestingly it works with `--release`, so I guess this is a Rust thing?...

I'm hitting this as well - workaround works, but would be nice to be built in.

Is there any progress on this PR? I run Developer Advocacy at Timescale, and I'd love to help out anywhere I can! We ❤️ Ruby, and we ❤️ what RubyGems...

So in the meantime, is there a command which pulls a single package into a depot?

As far as writing data there is no difference between Timescale and Postgres. It would be up to the user to configure the destination tables (and hypertables in the Timscaledb...

I forgot to note our progress here: this can be achieved using `PostgREST` (a REST gateway for PostgreSQL) . Performance is very good.