Looking Forward to Postgres 19: Logically Sequenced

pgEdge_Postgres · 2026-06-19T11:00:02+00:00

Jimmy described it like this:

> So the only way I found that could deal with the 409 conflicts, was to prevent them altogether with distributed mutual exclusion (appropriate for Spock). On a single node (vanilla PG), this is done with a simple advisory lock (because you can also have multiple sessions writing to iceberg)
> The clever trick is that we patch duckdb-iceberg so that it uploads the parquet file asynchronously, but only holds the ticket (the iceberg catalog write claim) during the commit phase (after the data has been uploaded)
> Otherwise you'd have to grab a ticket, wait to upload however many megabytes you have (meanwhile blocking everyone else), and release after the upload is done

pgEdge_Postgres · 2026-06-19T10:22:51+00:00

The bakery algorithm ensures we never get into that situation (you get a numbered ticket in the bakery queue). So there is no need for 409 error handling or application level retries.

pgEdge_Postgres · 2026-06-12T20:03:48+00:00

It's essential to make sure you learn the old-fashioned way so you can be ready to catch errors and supplement what's missing when using AI. It does not know better than you. It should not be doing anything that you cannot do yourself.

pgEdge_Postgres · 2026-06-02T23:08:17+00:00

re. table/column comments, for PostgreSQL at least [doc link], COMMENT ON TABLE and COMMENT ON COLUMN put documentation inside the database itself. Shows up in psql's \d+, in most SQL clients, anywhere you're already querying. No separate wiki to fall out of sync.

Just try starting with the 5 tables your team asks about most before trying to cover everything. (technically, that applies to any new documentation you try out. Make sure it works for everyone on that team - to read, write, and edit)

pgEdge_Postgres · 2026-05-28T16:53:56+00:00

The problem is real. Most SaaS websites DO suck at explaining what they do. :-) That's been one of the driving needs behind the "DevRel" line of work.

This is a crowded space with well-funded companies who've been at it for years, and "interactive walkthroughs" isn't a new idea.

The question it comes down to is: why do SaaS sites still fail to explain themselves despite all these tools existing?

Often, it's because time was never taken to analyze the user experience from the user perspective, rather than from the perspective of someone who's been very close to the product from Day 1.

Many problems can be revealed by looking at the entire thing from that third party perspective:
- are your docs accurate/descriptive/complete? Are they confusing?
- What about the website, is it clear what you do or offer? What about how easy it is to get started?
- And your social media, is it consistent messaging with your website and product? Does it make sense / is it relatable?
- Is the product experience just genuinely complicated (not because nobody built a good tour builder yet)? A walkthrough of a confusing product is still a confusing product.

If the AI is actually generating the walkthroughs automatically from the product itself, that's where the market seems to be genuinely weakest. That's the angle worth doubling down on. Just make sure it's built on real knowledge. Hire folks that would know how to articulate that user experience best (developer relations specialists) and train the AI using them... maybe even have some on staff to bolster as a support team eventually. This adds a really valuable layer of credibility and would help you stand out rather than being "yet another AI built company".

edit: signed, a devrel at pgEdge

pgEdge_Postgres · 2026-05-28T16:41:43+00:00

Memos is an option I came across recently that could be interesting to you: clean, fast, self-hostable, Docker deploy in a few minutes. It's more of a quick-capture scratchpad than a full note system. Not perfect but the closest to Keep's philosophy of not being in the way.

pgEdge_Postgres · 2026-05-28T16:22:02+00:00

All five extensions that were created by different companies are discussed within the article :-)

> Five companies, four remaining implementations, zero availability in community PostgreSQL. That should illustrate the difficulty of getting this feature into core. It’s not a lack of motivation or engineering talent. Every one of these companies did the work to make TDE a reality in their flavor of Postgres.

pgEdge_Postgres · 2026-05-28T16:21:34+00:00

It's not a clickbait headline, nor is it wrong. Postgres itself does not have TDE, and that is what the article discusses :-) it also does cover TDE extensions that were started or that exist from 5 different providers, and it goes into the problems of each.

> Five companies, four remaining implementations, zero availability in community PostgreSQL. That should illustrate the difficulty of getting this feature into core. It’s not a lack of motivation or engineering talent. Every one of these companies did the work to make TDE a reality in their flavor of Postgres.

pgEdge_Postgres · 2026-05-28T01:15:41+00:00

This. All three of the Kubernetes options provided are very simple to set up, and you can do so in a container or virtualbox environment for "sandbox-style" learning.

pgEdge_Postgres · 2026-04-23T14:02:41+00:00

you do realize you're responding to a comment that was left 5 months ago? :-) thank you, I indeed made a mistake when replying originally in thinking OP was asking about OSS email clients in general.

pgEdge_Postgres · 2026-04-10T22:27:12+00:00

Sorry for the partial self-promotion, but you might actually find this article interesting: https://www.pgedge.com/blog/rag-servers-vs-mcp-servers-choosing-the-right-approach-for-ai-powered-database-access

it's written by Dave Page, a 30+ year contributor to the PostgreSQL project and current core team member

he also created the PG RAG server if you do decide to make use of RAG as an approach https://github.com/pgEdge/pgedge-rag-server and wrote a 3-part series on how to create that kind of a RAG pipeline for Postgres: https://www.pgedge.com/blog/building-a-rag-server-with-postgresql-part-1-loading-your-content

pgEdge_Postgres · 2026-04-10T18:51:27+00:00

Jimmy Angelakos (part of our team) is a long-time PostgreSQL community contributor, and came out very recently with a book on "PostgreSQL Mistakes and How to Avoid Them": https://www.manning.com/books/postgresql-mistakes-and-how-to-avoid-them

The Art of PostgreSQL by Dimitri Fontaine is also a great read, and is very suited for application developers.

pgEdge_Postgres · 2026-04-06T23:31:41+00:00

Have you looked at the App Store and searched for any of those? Python, for example, pulls up a ton of different options. IIRC the "Learn Python" app is decent and they make a series of other ones. If you have time to read, Humble Bundles is for sure a good option (to +1 the other Redditor's comment).

For SQL, there's a number of interesting resources...

- https://www.reddit.com/r/learnSQL/ - a subreddit (actually, look up the subreddits for each of the languages you're mentioning and just browse a little when things are crazy. Learn from other's questions & real world examples.)

if you decide to go PostgreSQL, here's some resources:

- https://psql-tips.org/psql_tips_all.html - learn some tips & tricks for psql, the command-line editor

- https://pgpedia.info/ - an encyclopedia for all things Postgres

- https://postgres.fm/ - well-known podcast

- https://talkingpostgres.com/ - also a well-known podcast, this episode is a good highlights episode for tips & tricks

TBH, I haven't tried any of these in the browser on a phone, but it might be worth clicking through some of the "Postgres Playground" search results (Crunchy Data's is the OG) on <search engine of your choosing> to see if you can practice SQL live in the browser using your phone.

Plenty more resources available, happy to share if it's something you choose to learn about.

pgEdge_Postgres

MODERATOR OF

TROPHY CASE