1321
Topics /
Databases & Data
The most popular blog posts about databases & data on Hacker News. 2,337 posts.
1322
Gemini API File Search is now multimodal
Updates to the Gemini API File Search tool makes building efficient, multimodal file retrieval systems easier for developers.
1323
1324
Speeding up PostgreSQL dump/restore snapshots
How targeted improvements helped us speed up bulk data loads and complex schemas.
1325
Introducing pgzx: create PostgreSQL extensions using Zig
We are excited to introduce pgzx, a framework for creating Postgres extensions using the Zig programming language.
1326
1327
1328
Performance Benchmark 2018 – MongoDB, PostgreSQL, OrientDB, Neo4j and ArangoDB
The only enterprise AI data platform that cuts complexity, reduces costs, and gets you to production faster.
1329
Using Postgres for Everything
What Postgres for Everything means to a dev deploying all sorts of databases. Spoiler: it’s about collapsing your stack and keeping it simple.
1330
I rewrote PostHog's SQL parser, 70x faster, while barely looking at the code
After the success of using agents to improve query performance through autoresearch , I wanted to try something more ambitious. I rewrote PostHog's…
1331
1332
RethinkDB 2.1.5 performance and scalability
This report describes a recent effort that the RethinkDB team took to measure our database product, RethinkDB, under different workloads and in different clustering configurations. We seek to provide a general overview of RethinkDB’s performance metrics for a variety of workloads and potential use cases. In this…
1333
Why Percentiles Don’t Work the Way We Think
Customers ask us for p99 (99th percentile) of metrics pretty frequently. We plan to add such a feature to Database Performance Monitor (DPM)(more on that later). But a lot of the time, when customers make this request, they have something very specific, and different, ...
1334
ChatGPT plugins now support Postgres and Supabase
Supabase recently contributed to the OpenAI Retrieval Plugin repo with a Postgres and a Supabase implementation to help developers build ChatGPT plugins using pgvector.
1335
1336
The four pillars of data observability: metrics, metadata, lineage, and logs
How much data is enough for observability? Learn the key pillars that describe your data and underpin data observability practices in 2024.
1337
1338
1339
ListenBrainz moves to TimescaleDB
The ListenBrainz team has been working hard on moving our primary listen store from InfluxDB to TimescaleDB , and today at UTC 16:00 we’re going to make the switch.
1340
Invention of DNA "page numbers" opens up possibilities for the bioeconomy
A major technological advance in DNA writing enables researchers to construct and create in the language of biology
1341
1342
MariaDB 10.1 can do 1M queries per second
MariaDB 10.1 not only contains tons of new features, it has also been polished to deliver top performance. The biggest improvement has been achieved for scalability on massively multithreaded hardware. The following numbers show the throughput for a simplified sysbench OLTP benchmark on MariaDB-10.1.8 compared to…
1343
1344
1345
PostgreSQL 16 Beta 1
The PostgreSQL Global Development Group announces that the first beta release of PostgreSQL 16 is now [available for download](https://www.postgresql.org/download/). This …
1346
RethinkDB 1.14: binary data, seamless migration, and Python 3 support
Upgrading on Ubuntu? If you’re upgrading from 1.12 or earlier, first set up the new RethinkDB PPA .
1347
Announcing Apache Spark 1.4
Apache Spark 1.4 introduces SparkR, new DataFrame features, ML pipelines, and enhanced visualization and monitoring tools for better production debugging.
1348
Looking Forward to Postgres 19: It's About Time
Postgres 19 brings native temporal table support. Shaun Thomas covers WITHOUT OVERLAPS, FOR PORTION OF, and temporal foreign keys - and what's still missing.
1349
Google acquires Metaweb (Freebase)
Insights from Googlers into our products, technology, and the Google culture
1350
Postgres geography type is not limited to Earth
It's a little known fact that the PostGIS geography type since PostGIS 2.2 (well was introduced in 2.1 I think but had a bug in it until 2.1.4 or so), supports any spheroidal spatial reference system that measures in degrees. When an srid is not specified, it defaults to using 4326, Earth WGS 84 long lat.