--- title: PostgreSQL adapter for Python | daily.dev description: Psycopg 2.4.1, the popular PostgreSQL adapter for Python, has been released with several bug fixes. Notable changes include a new bundled parser for bytea... canonical: https://daily.dev/posts/postgresql-adapter-for-python-yn2k8o0mg twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: PostgreSQL adapter for Python | daily.dev og:description: Psycopg 2.4.1, the popular PostgreSQL adapter for Python, has been released with several bug fixes. Notable changes include a new bundled parser for bytea... og:url: https://daily.dev/posts/postgresql-adapter-for-python-yn2k8o0mg og:image: https://api.daily.dev/og/posts/yn2K8O0mg.png og:image:alt: PostgreSQL adapter for Python og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # PostgreSQL adapter for Python **[Psycopg](https://daily.dev/sources/psycopg)** · 1 min read · 0 upvotes · 0 comments ## Summary Psycopg 2.4.1, the popular PostgreSQL adapter for Python, has been released with several bug fixes. Notable changes include a new bundled parser for bytea output that removes the dependency on libpq 9.0 for hex format parsing, a fix preventing connection failures with non-normalized client encodings, correct detection of empty queries sent to the backend, a fix for a SystemError that clobbered libpq errors lacking SQLSTATE, a fix for the interaction between NamedTuple and server-side cursors, and the ability to pass --static-libpq directly on the setup.py command line. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### What changed in psycopg 2.4.1 regarding bytea output parsing? Psycopg 2.4.1 uses its own parser for bytea output instead of relying on libpq to parse the hex format, which removes the previous requirement of having libpq 9.0 installed to handle hex-encoded bytea values from PostgreSQL. _daily.dev helps Python developers track adapter releases like this before a libpq version mismatch breaks a deploy._ ### Does psycopg 2.4.1 fix the connection failure caused by non-normalized client encoding? Yes, psycopg 2.4.1 fixes a bug where connections would fail if the client encoding was a non-normalized variant, an issue originally reported by Peter Eisentraut. Connections now succeed even when the encoding string is not in its normalized form. _Developers debugging PostgreSQL connection encoding issues can follow driver fixes like this on daily.dev._ ### What was the SystemError bug fixed in psycopg 2.4.1? Psycopg 2.4.1 fixes a SystemError that clobbered libpq errors raised without an SQLSTATE code, meaning such errors were previously masked by a generic Python SystemError instead of surfacing the actual libpq error. The bug was diagnosed by Eric Snow. _daily.dev keeps developers hunting obscure driver errors current on fixes like this psycopg patch._ --- Tags: [#python](https://daily.dev/tags/python), [#postgresql](https://daily.dev/tags/postgresql) [View this post on daily.dev](https://daily.dev/posts/postgresql-adapter-for-python-yn2k8o0mg) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"PostgreSQL adapter for Python","url":"https://daily.dev/posts/postgresql-adapter-for-python-yn2k8o0mg","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/postgresql-adapter-for-python-yn2k8o0mg"},"datePublished":"2026-08-23T12:22:04.065Z","dateModified":"2026-08-23T12:44:11.235Z","description":"Psycopg 2.4.1, the popular PostgreSQL adapter for Python, has been released with several bug fixes. Notable changes include a new bundled parser for bytea...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/b0cbd2ac8948f96ab39fa6a90db7464f?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/b0cbd2ac8948f96ab39fa6a90db7464f?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Psycopg","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Psycopg","logo":"https://media.daily.dev/image/upload/s--5N-KNNWk--/f_auto,q_auto/v1787487485/logos/psycopg?_a=BAMAMicg0","url":"https://daily.dev/sources/psycopg"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/postgresql-adapter-for-python-yn2k8o0mg","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"python,postgresql","timeRequired":"PT1M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Psycopg","item":"https://daily.dev/sources/psycopg"},{"@type":"ListItem","position":3,"name":"PostgreSQL adapter for Python"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/postgresql-adapter-for-python-yn2k8o0mg#faq","mainEntity":[{"@type":"Question","name":"What changed in psycopg 2.4.1 regarding bytea output parsing?","acceptedAnswer":{"@type":"Answer","text":"Psycopg 2.4.1 uses its own parser for bytea output instead of relying on libpq to parse the hex format, which removes the previous requirement of having libpq 9.0 installed to handle hex-encoded bytea values from PostgreSQL. daily.dev helps Python developers track adapter releases like this before a libpq version mismatch breaks a deploy."}},{"@type":"Question","name":"Does psycopg 2.4.1 fix the connection failure caused by non-normalized client encoding?","acceptedAnswer":{"@type":"Answer","text":"Yes, psycopg 2.4.1 fixes a bug where connections would fail if the client encoding was a non-normalized variant, an issue originally reported by Peter Eisentraut. Connections now succeed even when the encoding string is not in its normalized form. Developers debugging PostgreSQL connection encoding issues can follow driver fixes like this on daily.dev."}},{"@type":"Question","name":"What was the SystemError bug fixed in psycopg 2.4.1?","acceptedAnswer":{"@type":"Answer","text":"Psycopg 2.4.1 fixes a SystemError that clobbered libpq errors raised without an SQLSTATE code, meaning such errors were previously masked by a generic Python SystemError instead of surfacing the actual libpq error. The bug was diagnosed by Eric Snow. daily.dev keeps developers hunting obscure driver errors current on fixes like this psycopg patch."}}]} ```