<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Postgresql on nanta - Data Engineering</title><link>https://nanta-data.dev/en/tags/postgresql/</link><description>Recent content in Postgresql on nanta - Data Engineering</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>© 2026 nanta</copyright><lastBuildDate>Fri, 27 Feb 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://nanta-data.dev/en/tags/postgresql/index.xml" rel="self" type="application/rss+xml"/><item><title>Superset: Resolving Six User-Reported Issues</title><link>https://nanta-data.dev/en/posts/superset-user-reported-issues/</link><pubDate>Fri, 27 Feb 2026 00:00:00 +0000</pubDate><guid>https://nanta-data.dev/en/posts/superset-user-reported-issues/</guid><description>Our data governance team reported six issues they found while using Superset. From a missing .png extension on Slack screenshots to a CSV download 500 error caused by PostgreSQL&amp;rsquo;s idle_in_transaction_session_timeout killing the metadata DB connection mid-download. The trickiest one required tracing through both Superset server logs and RDS error logs to discover that the error connection and the causal connection were different — the SSL error was on the metadata DB, not Redshift.</description></item></channel></rss>