Giovanni Martinez

Today marks day one of an exciting new chapter! 🚀 I’m thrilled to announce I’m joining @TigerDatabase (formerly Timescale) as a Database Support Engineer. I'll be taking my passion for #PostgreSQL helping teams architect high-performance, AI-ready data systems. Time to build!

Compared DocumentDB vs Aurora PostgreSQL for JSON workloads and, the biggest surprises? Not where you'd expect: query flexibility, indexing, among others. Full breakdown here 👇 dub.sh/aK3117C

I always wanted quick, no-fuss Postgres tools for everyday use, so I finally built them. I now use my own toolkit daily to: ⚡️ Build connection strings ⚡️ Format complex queries ⚡️ Analyze pg_stat_statements Built for DBAs, by a DBA. What do you need next? thepostgresguy.com

News: Join Us at PGDay Armenia 2026 in Yerevan on April 30, 2026 postgresql.org/about/news/joi…

News: PGConf.dev 2026 Schedule Announced! postgresql.org/about/news/pgc…

I took a little break, but I'm excited to be back sharing with you all. Here’s what I’ve been working on lately—can’t wait for your thoughts! Check it out! dub.sh/noZnfCt

I’m absolutely thrilled to announce I've joined the AWS Community Builders 2026 cohort! ☁️🚀 My first official deep dive is here: dub.sh/2SOq1v7

I've spent a lot of time thinking about how tough it is to keep our data safe. Each setup—on-prem, hybrid, or cloud—has its own security headaches. Personally, I find hybrid setups trickiest because of juggling different policies and controls. What’s your experience?

I always find myself choosing between a detailed HTML report and a quick terminal summary. I really like seeing a clear summary of my test results, but sometimes a visual report helps me spot issues faster. What works best for you? Let me know your thoughts!

I’ve tried a few different operating systems for managing databases, and each one has its own perks. I use MacOS for most of my database work because it feels stable and flexible. What OS do you prefer for database management? Let me know in the comments!

A key insight from Chapter 7 of PostgreSQL Internals Mastery: If your UPDATE touches an indexed column, you pay a "tax" by rewriting the index. . Live event: dub.sh/pXAG8Yz Grab the book: dub.sh/2ScbLeO

"Just add an index" is the "Have you tried restarting?" of databases. 📉 We're building 𝗶𝗾𝘁𝗼𝗼𝗹𝗸𝗶𝘁 to give you a second opinion. It tells you where the damage is happening. What’s the one automated Mongo insight you wish you had right now? 👇 #MongoDB #iqtoolkit #Database

IQToolkit Analyzer v0.3.0rc1 is out on TestPyPI. This RC focuses on contracts-first outputs, config validation, and CLI UX polish. Try it and share feedback. Install (RC): - pip: `pip install iqtoolkit-analyzer==0.3.0rc1

Postgres hides the problem (silent locks). MongoDB buries it (millions of log lines). 💀 We’re building 𝗶𝗾𝘁𝗼𝗼𝗹𝗸𝗶𝘁 to catch both the Postgres Ghost Lock and the Mongo Scan Storm automatically. Stop grepping. Let the tool solve it. #DevOps #MongoDB #Postgres #iqtoolkit

I finally finished getting the CLI for iqtoolkit-analyzer into Homebrew! Here's what you need to know to install it once v0.3-rc3 is released. Stay tuned for more updates!

Postgres logs. Mongo slow query logs. Profiler output. Weird formats everywhere. If you assume clean input, your “AI analysis” is fiction. IQToolkit is a second-opinion layer for Postgres + MongoDB: explain why it’s slow and what to fix first (Glass Box, not black box).

I wrote a deep dive on these mechanics, including how to choose between EXTENDED, EXTERNAL, and MAIN storage strategies. If you care about DB performance, read the full breakdown here: iqtoolkit.ai/blog/postgresq… #Database #SystemDesign #SQL

Come hang out with me live as I walk through the new features and answer your questions in real time! Join me live for a deep dive into IQToolkit Analyzer v0.3.0. See how we blend PostgreSQL and MongoDB analysis in one tool. Drop by and ask me live! tinyurl.com/4h5s2fmb

Three practical rules to stop fighting TOAST: Isolate massive columns into their own tables. Monitor TOAST table growth separately from the main relation. Be wary of UPDATE: Even if you don't touch the big column, you might trigger hidden rewrites.@PostgreSQL

I always thought PostgreSQL handled big data smoothly—until I hit a surprising snag. Let me show you what really happens behind the scenes when your tables start growing. Curious? Check out my latest video and let me know what you think! dub.sh/wFDw3mr