Work in progress: 181,232 of 181,233 sites checked so far, more every week · updated 2 Nov 2026Missing a blog? Tell us

Top all-time · #2113

P

Postgres Professional Europe Limited

Company blog · postgrespro.com/blogdataprogramming

Postgres Professional Europe Limited is the company blog at postgrespro.com, writing about data and programming. Since 2016, 36 different Hacker News readers have linked it 41 times, most often “PostgreSQL 14 Internals Book”. It is still writing: the last post was on 2026-10-23, and you can follow it by feed.

Visit the blog
41mentions?
36HN people?
2016–2025first – last linked?
Links on Hacker News per year · peak 14 in 2023

Too few sampled comments (28) to say how often HN recommends it.?

Why HN links it

HN readers link Postgres Professional's site for its free PostgreSQL 14 Internals book, online courses, and mailing-list archives on PostgreSQL development and internals. Commenters point to it for explaining transaction isolation and MVCC.

Summarised by Claude from a sample of 28 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.

Postgres Professional is a PostgreSQL company delivering Postgres Pro DBMS and all kinds of PostgreSQL professional services worldwide

Most-linked posts?

  1. PostgreSQL 14 Internals Book
    8 people · 8 mentions · first linked 2022-07-13
  2. /list/thread-id/1853280
    2 people · 2 mentions · first linked 2022-07-11
  3. /list/thread-id/2505440
    2 people · 2 mentions · first linked 2025-04-03

What Hacker News says?

  1. I think the simple answer is philosophy of Kaizen(改善)- continuous improvement. I started working with postgresql when it was just postgres95. Recently found that my earliest question on postgresql-users was 13th October 1998, 20 years ago ( https://postgrespro.com/list/id/3.0.2.32.19981013214318.0069... ). I still use PostgreSQL in my startup for almost all critical production workload. This in itself a testament to…

    Comment linking /list/id/3.0.2.32.19981013214318.006939a4@chemquick.com

    on “PostgreSQL 11 Released”
  2. Submitted PostgreSQL 14 Internals Book as a story · 452 points

    HN discussion
  3. Thank you matashii--this would definitely explain it. I've also received another email suggesting this anomaly is due to the difference in commit/visibility order between primary and secondary. Is there by chance a writeup of this available anywhere that I can link to? It looks like https://postgrespro.com/list/thread-id/1827129 miiight be related, but I'm not certain. If so, I'd like to update the report. My email…

    Comment linking /list/thread-id/1827129

    on “Jepsen: Amazon RDS for PostgreSQL 17.4”
  4. Submitted PostgreSQL 14 Internals book – Part II as a story · 240 points

    HN discussion
  5. I know there used to be some O(n^2) logic associated with notify. Anyone know if that ever got fixed? Cursory search only turns up https://postgrespro.com/list/thread-id/2407396 The benchmark shows that the time to send notifications grows quadratically with the number of notifications per transaction without the patch while it grows linearly with the patch applied and notification collapsing disabled.

    Comment linking /list/thread-id/2407396

    on “Postgres is a great pub/sub and job server (2019)”
  6. Submitted Locks in PostgreSQL: Locks in Memory as a story · 4 points

    HN discussion
  7. That's not exactly true. You can write your own patch for a feature and there's a good chance they'll decide they don't want it. It's their prerogative, but also slightly upsetting when you know they're blocking features you want. Just observe the bike shedding over a trailing commas patch [1]. 1. https://postgrespro.com/list/thread-id/1853280

    Comment linking /list/thread-id/1853280

    on “Postgres 15 improves UNIQUE and NULL”
  8. Submitted PostgreSQL 17: part 3 or CommitFest 2023-11 Review as a story · 3 points

    HN discussion
  9. And there's also https://postgrespro.com/docs/enterprise/current/multimaster With a history behind it.

    Comment linking /docs/enterprise/current/multimaster

    on “Pgactive: Postgres active-active replication extension”
  10. Submitted Postgres for Developers as a story · 3 points

    HN discussion
  11. justinclift · 2025-02-13Recommends
    This is a bit older now, but seems like it covers the timeless basics: https://postgrespro.com/community/courses/DBA1

    Comment linking /community/courses/DBA1

    on “PgAssistant: OSS tool to help devs understand and optimize PG performance”
  12. Submitted PostgreSQL for Beginners as a story · 3 points

    HN discussion
  13. IMHO, with this type of issue is often more likely blowing through the multixact cache or the query planner reverting to SEQSCAN due to the number of locks or mxact id exaustion etc.. It is most likely not a WAL flush problem that commit_delay would help with. From the above link:[1] > I found that performing extremely frequent vacuum analyze (every 30 minutes) helps a small amount but this is not that helpful so pr…

    Comment linking /list/thread-id/2505440

    on “Show HN: Hatchet v1 – A task orchestration platform built on Postgres”
  14. Submitted Postgres 14 Internals Book as a story · 2 points

    HN discussion
  15. I'm not sure of the exact threshold, but the pathological case seemed to be (1) many tasks in the backlog, (2) many workers, (3) workers long-polling the task tables at approximately the same time. This would consistently lead to very high spikes in CPU and result in a runaway deterioration on the database, since high CPU leads to slower queries and more contention, which leads to higher connection overhead, which l…

    Comment linking /list/thread-id/2505440

    on “Show HN: Hatchet v1 – A task orchestration platform built on Postgres”
  16. Submitted What are the best practices for harnessing LLM within Postgres? as a story · 1 points

    HN discussion
  17. I was recently bit doing a Postgres upgrade by the Postgres team considering statements like `select 1 group by true` fine to silently break in Postgres 15. See https://postgrespro.com/list/thread-id/2661353 - and this behavior remains undocumented in https://www.postgresql.org/docs/release/ . It's an absolutely incredible project, and I don't disagree with the decision to classify it as wontfix - but it's an anecdo…

    Comment linking /list/thread-id/2661353

    on “Postgres UUIDv7 and per-back end monotonicity”
  18. Submitted Ask HN: Feedback on supporting AI queries in Postgres as a story · 1 points

    HN discussion
  19. https://postgrespro.com/list/thread-id/1853280

    Comment linking /list/thread-id/1853280

    on “How about trailing commas in SQL?”
  20. Submitted Deep Dive into PostgreSQL Statistics as a story · 1 points

    HN discussion
  21. brasetvik · 2025-03-03Recommends
    Also recommend this free book: https://postgrespro.com/community/books/internals

    Comment linking /community/books/internals

    on “The Internals of PostgreSQL”
  22. Submitted PostgreSQL 14 Internals (2023, PDF) as a story · 1 points

    HN discussion
  23. And machine learning in on the way - https://postgrespro.com/roadmap/56513

    Comment linking /roadmap/56513

    on “Baidu Takes FPGA Approach to Accelerating SQL at Scale”
  24. Submitted Locks in PostgreSQL: Locks in Memory as a story · 1 points

    HN discussion
  25. > PostgreSQL 10 provides native partitioning. Despite the flexibility, this approach forces the planner to perform an exhaustive search and to check constraints on each partition to determine whether it should be present in the plan or not. Large amount of partitions may result in significant planning overhead. > The pg_pathman module features partition managing functions and optimized planning mechanism which utili…

    Comment linking /products/extensions/pg_pathman

    on “TimescaleDB vs. InfluxDB: built differently for time-series data”
  26. Submitted Millions of Queries per Second: PostgreSQL and MySQL’s Peaceful Battle as a story · 1 points

    HN discussion
  27. > pgSQL is still not quite there when compared to PL/SQL. Yes, but maybe it's a good thing after all. pgSQL is small, and mostly clear and restrictive, there's no bunch of imperative features and dark corners. The main point of PostgreSQL always was extendability, so it supports a broad list of programming languages for stored procedures. To address efficiency concerns, executor's JIT is on the way - https://postgre…

    Comment linking /roadmap/56509

    on “Four DB2 Code Bases?”
  28. Use named prepared statements (the ones where you have to manually DEALLOCATE to free up resources on the server). It is to my understanding that a named prepared statement runs five times using both a custom query plan and a generic query plan, and from the sixth execution onwards it picks the faster of the two and sticks to it for the rest of the prepared statement's lifetime (the query planner never gets called a…

    Comment linking /list/thread-id/2070689

    on “A Hairy PostgreSQL Incident”
  29. Another neat Postgres 15 feature: SQL 2016 Standard JSON operator support https://postgrespro.com/blog/pgsql/5969433

    Comment linking /blog/pgsql/5969433

    on “Upcoming feature in PostgreSQL 15 – MERGE statement”
  30. > at one point in the last 10 years they still used sunos4 as their base configuration because you know, What exactly do you mean with this? I tried to find some more information, and all I could find were some fixes from 2001[1] (SunOS 4 was supported until 2003), a minor refactor in 2008 with "SunOS 4 is probably broken anyway"[2], and that's pretty much it. SunOS 4 was moved to "Unsupported Platforms" with the re…

    Comment linking /list/thread-id/1598869

    on “Ask HN: It's 2023, how do you choose between MySQL and Postgres?”

Search all of HN for postgrespro.com

Linked by the same people?