https://www.postgresscripts.com/tags/pg_sequences/Recent content in Pg_sequences on Postgres ScriptsHugo -- gohugo.ioenPostgresScripts.comSat, 20 Jun 2026 00:00:00 +0000https://www.postgresscripts.com/post/inspect-postgresql-sequences-with-pg-sequences/Sat, 20 Jun 2026 00:00:00 +0000https://www.postgresscripts.com/post/inspect-postgresql-sequences-with-pg-sequences/ <h2 id="inspect-postgresql-sequences-with-the-pg_sequences-view">Inspect PostgreSQL Sequences with the pg_sequences View</h2> <p><code>pg_sequences</code> is the catalog-backed view that exposes every sequence in the current database in one readable row each — <code>start_value</code>, <code>min_value</code>, <code>max_value</code>, <code>increment_by</code>, <code>cache_size</code>, <code>cycle</code>, and the all-important <code>last_value</code>. It turns a scattered set of per-sequence <code>currval()</code> lookups into a single audit query.</p> <script async src="https://pagead2.googlesyndication.com/pagead/js/adsbygoogle.js?client=ca-pub-1012089347386563" crossorigin="anonymous"></script> <ins class="adsbygoogle" style="display:block" data-ad-client="ca-pub-1012089347386563" data-ad-slot="7945792173" data-ad-format="auto" data-full-width-responsive="true"></ins> <script> (adsbygoogle = window.adsbygoogle || []).push({}); </script> <h2 id="purpose-and-overview">Purpose and Overview</h2> <p>Sequences are easy to create and easy to forget. Every <code>SERIAL</code> or <code>GENERATED AS IDENTITY</code> column quietly relies on a sequence object to hand out the next number, and most of the time nobody looks at one until an <code>INSERT</code> fails with a &quot;nextval: reached maximum value&quot; error. By then the table is blocked for new rows and the fix has to happen under pressure.</p>