Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
jamesgresql
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
6 ms
·
31.
▲
by
jamesgresql
1y ago
Tiger here, let's go!
32.
▲
Benchmarking Postgres Batch Ingest
(timescale.com)
1 points
by
jamesgresql
2y ago
|
1 comments
33.
▲
by
jamesgresql
2y ago
Hi HN! I've been benchmarking again, this time looking at all the permutations of COPY and INSERT in Postgres. Let me know what you think.
34.
▲
Boosting Postgres Insert Performance by 50% with Unnest
(timescale.com)
4 points
by
jamesgresql
2y ago
|
2 comments
35.
▲
by
jamesgresql
2y ago
Hi HN! If you're interested in PostgreSQL or database performance here's a short benchmark I did looking into the seemingly magical performance gain you can get by INSERTing unnested arrays rather than VALUES tuples in Postgres. L
36.
▲
SkipScan Under Load
(timescale.com)
8 points
by
jamesgresql
2y ago
|
1 comments
37.
▲
by
jamesgresql
2y ago
Hi HN! I wrote this article comparing TimescaleDB's SkipScan feature to vanilla Postgres performance for DISTINCT queries (get me the last row for all IDs) while a 200K rows per second ingest was happening. I'm going to be writing
38.
▲
Why we moved away from K8s StatefulSets
(timescale.com)
3 points
by
jamesgresql
2y ago
|
0 comments
39.
▲
Petabye Postgres
(timescale.com)
5 points
by
jamesgresql
2y ago
|
1 comments
40.
▲
by
jamesgresql
2y ago
Our Insights product at Timescale recently ticked over 1 petabyte of storage, 100 trillion metrics stored, 800 billion metrics per day. A lot of the data is stored using Timescale's Tiering feature, but all that data is still ingested
41.
▲
by
jamesgresql
2y ago
Great comments! This is exactly where we see ourselves contributing: both making pgvector faster and more efficient through pgvectorscale, and working to make the AI on Postgres developer experience first class.
42.
▲
by
jamesgresql
2y ago
Super excited about this launch, happy to answer any questions (or jump into our Discord for more) The pgvectorscale repo is at: https://github.com/timescale/pgvectorscale
43.
▲
by
jamesgresql
2y ago
(Author here) Oh for sure! This is specifically about databases, databases can't do it all (unless you use Omnigres I suppose?)
44.
▲
by
jamesgresql
2y ago
(Author here!) I'd compare performance to what you need, not to other technology. But also, point taken. The article this comment thread describes also needs to be written.
45.
▲
by
jamesgresql
2y ago
Author here, this is obviously a high level post! There are many, many posts about how Postgres with different extensions can get you different things. I didn't want to go down that path for this article because I didn't want it t
46.
▲
by
jamesgresql
2y ago
Just out of interest what would you say a 'higher throughput' was?
47.
▲
Row vs. Columnar
(tiktok.com)
1 points
by
jamesgresql
2y ago
|
0 comments
48.
▲
by
jamesgresql
2y ago
Authour here: I know people either love or hate Postgres for Everything, either way I'd love some lively discussion!
49.
▲
Postgres for Everything: keep your tech stack simple –> get more time to build
(tsdb.co)
1 points
by
jamesgresql
2y ago
|
1 comments
50.
▲
by
jamesgresql
2y ago
Hi, we updated our docs with the best options. https://docs.timescale.com/self-hosted/latest/install/instal... I'd personally recommend StackGres, it's a great project.
51.
▲
by
jamesgresql
2y ago
This is super cool! I run DevlRel @ Timescale, and I love seeing our community create well written posts like this! My initial reaction is that I think one of the reasons you're seeing a hypertable being slower is almost certainly that
52.
▲
by
jamesgresql
3y ago
Great book!
53.
▲
by
jamesgresql
3y ago
(:alert: I work for Timescale :alert:) It's funny, we hear this more and more "we did some research and landed on Influx and ... help it's confusing". We actually wrote an article about what we think, you can find it her
54.
▲
by
jamesgresql
3y ago
I'm really excited about the COPY FROM improvements! Can't wait to test them with some big data.
55.
▲
by
jamesgresql
4y ago
Just a quick note that Timescale is just an extension for Postgres, not a “switch” of database. It’s as easy as: CREATE EXTENSION timescaledb: SELECT create_hypertable('table_name', 'time_column_name', chunk_ti
56.
▲
by
jamesgresql
4y ago
Hello! I run Developer Advocacy at Timescale. Easy fix - we can do a benchmark comparing TimescaleDB to pg_partman. Longer reply: pg_partman does address many of the same developer experience items we do, but it doesn't offer things li