<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/agents-gone-awry-on-postgres-sboms-start-over-saxdpveyt" -->

---
title: Agents Gone Awry on Postgres SBOMs: Start Over | daily.dev
description: A developer walks through a chaotic, week-long redesign of SBOM (Software Bill of Materials) generation and provenance attestation for CloudNativePG Postgres...
canonical: https://daily.dev/posts/agents-gone-awry-on-postgres-sboms-start-over-saxdpveyt
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: Agents Gone Awry on Postgres SBOMs: Start Over | daily.dev
og:description: A developer walks through a chaotic, week-long redesign of SBOM (Software Bill of Materials) generation and provenance attestation for CloudNativePG Postgres...
og:url: https://daily.dev/posts/agents-gone-awry-on-postgres-sboms-start-over-saxdpveyt
og:image: https://api.daily.dev/og/posts/SAXDpvEyT.png
og:image:alt: Agents Gone Awry on Postgres SBOMs: Start Over
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.

# Agents Gone Awry on Postgres SBOMs: Start Over

**[Planet PostgreSQL](https://daily.dev/sources/planet-postgresql)** · 4 min read · 1 upvotes · 0 comments

## Summary

A developer walks through a chaotic, week-long redesign of SBOM (Software Bill of Materials) generation and provenance attestation for CloudNativePG Postgres extension containers, built heavily with AI coding agents like Codex. The first design accidentally produced inconsistent verification commands between Debian-based and PGRX-based extension images, forcing a full restart using Docker's custom SBOM generator feature instead. The author notes AI agents accelerated the coding but could not determine the correct architectural design themselves - that required human judgment about goals and priorities. The related CNPG-Extensions Project, offering more automation than upstream, is available for testing with extensions like PG-Cron and PG-Partman.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://postgr.es/p/9uE>

## Questions this post answers

### How can I generate a custom SBOM for a Docker container image instead of relying on the default generator?

Docker supports providing a custom SBOM generator, allowing you to plug in your own module for composing the software bill of materials rather than using the built-in default. This approach was used to redesign a Postgres extension container project so that most SBOM logic lives in a self-contained sbom-generator module, keeping required build pipeline changes minimal.

_Developers standardizing container provenance workflows can follow ongoing SBOM design discussions on daily.dev._

### Why would PGRX-based Postgres extension builds need different verification commands than Debian-based ones?

Because PGRX builds originally ran under qemu emulation while Debian package builds did not, refactoring PGRX to use native GitHub Runners changed the resulting image structure, producing a completely different set of commands to validate security and provenance information for PGRX containers versus Debian-based ones. This inconsistency was judged too confusing for users and prompted a full redesign around a single verification approach.

_Teams building multi-architecture container pipelines can track provenance-consistency lessons like this via daily.dev._

## Similar posts on daily.dev

- [The agent is not the system. Postgres is.](https://daily.dev/posts/the-agent-is-not-the-system-postgres-is--hqvmc46rn) · Planet PostgreSQL · 1 upvotes · 0 comments

---

Tags: [#ai-agents](https://daily.dev/tags/ai-agents), [#docker](https://daily.dev/tags/docker), [#postgresql](https://daily.dev/tags/postgresql), [#sbom](https://daily.dev/tags/sbom)

[View this post on daily.dev](https://daily.dev/posts/agents-gone-awry-on-postgres-sboms-start-over-saxdpveyt)

```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":"Agents Gone Awry on Postgres SBOMs: Start Over","url":"https://daily.dev/posts/agents-gone-awry-on-postgres-sboms-start-over-saxdpveyt","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/agents-gone-awry-on-postgres-sboms-start-over-saxdpveyt"},"datePublished":"2026-09-15T21:50:05.003Z","dateModified":"2026-09-15T21:50:56.993Z","description":"A developer walks through a chaotic, week-long redesign of SBOM (Software Bill of Materials) generation and provenance attestation for CloudNativePG Postgres...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/517df7577cce591843a0a8333f3f6781?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/517df7577cce591843a0a8333f3f6781?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Planet PostgreSQL","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":"Planet PostgreSQL","logo":"https://media.daily.dev/image/upload/logos/placeholder.jpg","url":"https://daily.dev/sources/planet-postgresql"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/agents-gone-awry-on-postgres-sboms-start-over-saxdpveyt","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":1},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"ai-agents,docker,postgresql,sbom","timeRequired":"PT4M"}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Planet PostgreSQL","item":"https://daily.dev/sources/planet-postgresql"},{"@type":"ListItem","position":3,"name":"Agents Gone Awry on Postgres SBOMs: Start Over"}]}
{"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/agents-gone-awry-on-postgres-sboms-start-over-saxdpveyt#faq","mainEntity":[{"@type":"Question","name":"How can I generate a custom SBOM for a Docker container image instead of relying on the default generator?","acceptedAnswer":{"@type":"Answer","text":"Docker supports providing a custom SBOM generator, allowing you to plug in your own module for composing the software bill of materials rather than using the built-in default. This approach was used to redesign a Postgres extension container project so that most SBOM logic lives in a self-contained sbom-generator module, keeping required build pipeline changes minimal. Developers standardizing container provenance workflows can follow ongoing SBOM design discussions on daily.dev."}},{"@type":"Question","name":"Why would PGRX-based Postgres extension builds need different verification commands than Debian-based ones?","acceptedAnswer":{"@type":"Answer","text":"Because PGRX builds originally ran under qemu emulation while Debian package builds did not, refactoring PGRX to use native GitHub Runners changed the resulting image structure, producing a completely different set of commands to validate security and provenance information for PGRX containers versus Debian-based ones. This inconsistency was judged too confusing for users and prompted a full redesign around a single verification approach. Teams building multi-architecture container pipelines can track provenance-consistency lessons like this via daily.dev."}}]}
```

