Chris Riccomini’s Post

I published a 2 minute read on my blog about an easy way to get query specific metrics from PostgreSQL queries into an OpenTelemetry setup: https://lnkd.in/eGVX8_iB Let me know what you think!

Over on the Tembo blog, I've published a thinking-through of what all the jobs to be done of the ideal Postgres extension ecosystem might be.

🚀 Speed Up Compound Full-Text Searches in PostgreSQL by 300x https://lnkd.in/ebjhhFAv

🚀 New Blog Alert! 🚀 I'm excited to share that I've just published my latest article on "How to Use regexp_like in PostgreSQL?"! 🎉 👉 Check out the full article here: [https://lnkd.in/gZ_NrdKA]

Remember back in 2012, when PostgreSQL introduced JSON support ? https://lnkd.in/e_Qb8rpc Now in PostgreSQL 17 we have JSON_TABLE and new JSON functions !

In today's 5mins of #Postgres we discuss tuning the "work_mem" setting in Postgres for a given workload - and why its not as simple to set as you might think (or as it should be!). The most important aspect that I had to re-discover when researching this episode: The work_mem setting in Postgres is effective on a per-query execution node (aka plan node) basis, not for the whole query. That means for a query that e.g. does multiple sort or hashing operations, you will see a multiple of work_mem being used. In the episode we showcase that with an example, using pg_log_backend_memory_contexts(..) to dump the memory usage of a given connection. We feature a post by Shaun Thomas on the Tembo blog last week, as well as a few mailing list discussions, and a good post from Christophe Pettus last year. https://lnkd.in/gkqApSX6

Postgres 16 may be fresh and new, but PG15 isn’t a goner — far from it, it’ll likely be a step along your upgrade path. Discover its most relevant features and how to easily get there with a simplified major in-place upgrade with ClusterControl in this blog post.  #PostgreSQL15 #ClusterControl #DatabaseInnovation https://bit.ly/3TSBQJT

The future of Postgres? Stability and reliability are core to Postgres. New features will come from extensions, which allow developers to create other storage backends, new types, and more. There are a lot of extensions available. This article covers a few of the extensions that hint at the potential of Postgres' future. https://lnkd.in/dyXk2X7f

Written a blog on CRUD operations in PostgreSQL on Hashnode. If you are starting with postgres, do checkout. https://lnkd.in/gfU-WJ4y

How to setup read replica of PostgreSQL master ? Read replica is very useful when your system is read heavy. Sometime setting up replica is challenging both Sync and Async. I used docker containers to fork multiple instances of Postgres. One works as master and other as replica. Here is my medium article about setting up read-only replica of Postgres master. https://lnkd.in/dGX5pY8e