Postgres Write Speed: Don't Blame the Database, Blame the Method
A reader comment pushes back on the notion that PostgreSQL can't handle high-volume writes, arguing that the bottleneck is often the insertion approach rather than the engine itself.
The author points to the COPY statement as a far superior alternative to row-by-row inserts. When paired with the TimeScaleDB extension, they report sustaining write rates of 100,000 to 200,000 rows per second on tables with 50 to 100 columns.
Under those conditions, they suggest that ingesting one million key-value pairs should take well under four seconds, and likely far less. The writer clarifies they have no affiliation with either project, just a strong preference for both tools.
