Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1wxNhC-002gFR-0c for pgsql-bugs@arkaria.postgresql.org; Fri, 21 Aug 2026 11:46:02 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1wxNhB-00D996-0k for pgsql-bugs@arkaria.postgresql.org; Fri, 21 Aug 2026 11:46:01 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1wxL9X-00CWB9-0N for pgsql-bugs@lists.postgresql.org; Fri, 21 Aug 2026 09:03:07 +0000 Received: from mahout.postgresql.org ([2001:4800:3e1:1::227]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1wxL9V-00000001iXL-2d2m for pgsql-bugs@lists.postgresql.org; Fri, 21 Aug 2026 09:03:06 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=postgresql.org; s=20171124; h=Message-ID:Date:Reply-To:Cc:From:To:Subject: Content-Transfer-Encoding:MIME-Version:Content-Type:Sender:Content-ID: Content-Description:In-Reply-To:References; bh=3lzLUM7RJTEzgK2BAhlDxMBAcpwiRuCJI/6Ndkxv0m8=; b=j1MjRYk6WnRLgFjPVngBYFA01L kO8m1Y5StnLHUcaHOrUy25DaQLsvKW3gtiupMppjJsDMMjMMABxptT1D1WgfGkESz17QCsLS0W5xy PmZlVxRAvfHDRT56gbgWi9eK712V74HcejUj7o3n3nLseqaKQNPfECcXxGpVc+FUF92f137adjx/a N1YkTUIXPborpPQFaYyEhSbGzV4siIfjKm7ynDqWxk/d3qEFrUHceA4t0XoOl9WldEhQMmcHvIONx rfIxR7IuQWnTuNf7kXnE3GguCaPtJ+IfUfPvTL0lHCyLnDILWMZzQvAFf2uvCfgDBAnDbqlquWBc1 ORtwtpnA==; Received: from wrigleys.postgresql.org ([2a02:16a8:dc51::60]) by mahout.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1wxL9U-0059IK-22 for pgsql-bugs@lists.postgresql.org; Fri, 21 Aug 2026 09:03:05 +0000 Received: from localhost ([127.0.0.1] helo=wrigleys.postgresql.org) by wrigleys.postgresql.org with esmtp (Exim 4.98.2) (envelope-from ) id 1wxL9T-0000000DhI1-1Wfu for pgsql-bugs@lists.postgresql.org; Fri, 21 Aug 2026 09:03:03 +0000 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Subject: BUG #19635: Missing entry in information_schema.sequences when creating a Tale with auto increment To: pgsql-bugs@lists.postgresql.org From: PG Bug reporting form Cc: jonas-lugner@gmx.de Reply-To: jonas-lugner@gmx.de, pgsql-bugs@lists.postgresql.org Date: Fri, 21 Aug 2026 09:02:26 +0000 Message-ID: <19635-4a34f67d4340bd64@postgresql.org> X-Auto-Response-Suppress: All Auto-Submitted: auto-generated List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk The following bug has been logged on the website: Bug reference: 19635 Logged by: Missing entry in information_schema.sequences Email address: jonas-lugner@gmx.de PostgreSQL version: 16.15 Operating system: Alpine Linux via Docker Description: =20 When running the following code I expect that a entry is generated in information_schema.sequences, however this is not the case. CREATE TABLE users ( id INT GENERATED BY DEFAULT AS IDENTITY PRIMARY KEY );