<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Italian on Percona Community</title><link>https://percona.community/talk_tags/italian/</link><description>Recent content in Italian on Percona Community</description><generator>Hugo</generator><language>en-us</language><copyright>© Percona Community. MySQL, InnoDB, MariaDB and MongoDB are trademarks of their respective owners.</copyright><atom:link href="https://percona.community/talk_tags/italian/index.xml" rel="self" type="application/rss+xml"/><item><title>Avoiding pitfalls with Postgres and go</title><link>https://percona.community/talks/2026/2026-11-02-avoiding-pitfalls-with-postgres-and-go/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://percona.community/talks/2026/2026-11-02-avoiding-pitfalls-with-postgres-and-go/</guid><description>&lt;p>PostgreSQL is probably the most loved database to work with Go, for good reasons!&lt;/p>
&lt;p>As someone helping to scale many large postgres environments, some seemingly innocent choices end up being silent bottlenecks limiting the database possibilities.&lt;/p>
&lt;p>In this talk we will discuss less common tips on how to keep your postgres running happy with your go application.&lt;/p>
&lt;p>The goal is to guide you on how to stay flexible and prevent you from getting stuck in a position that would prevent you from scaling postgres in the future.&lt;/p></description></item></channel></rss>