|
|
|
|
|
|
by nh2
2825 days ago
|
|
|
Also, this is quite related (including gist I linked in comments): https://stackoverflow.com/questions/16916633/if-postgresql-c... Some of the issues magically got faster with `VACUUM ANALYZE`, but it would be great to know whether TimescaleDB can be tuned to support this out of the box so that it's always as fast as Elasticsearch. I have already written some scripts to preload postgres with an example data set; if I get some help with it, I could make that run against TimescaleDB, so that it can easily be evaluated whether it solves this use case, or whether it improves over time. |
|
|