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 1vzUsq-0013dB-1W for pgsql-general@arkaria.postgresql.org; Mon, 09 Mar 2026 07:18:32 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1vzUsn-00Ea8n-2T for pgsql-general@arkaria.postgresql.org; Mon, 09 Mar 2026 07:18:30 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vzUsn-00Ea8f-1R for pgsql-general@lists.postgresql.org; Mon, 09 Mar 2026 07:18:29 +0000 Received: from smtp.burggraben.net ([2a01:4f8:140:510a::3]) by magus.postgresql.org with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1vzUsl-00000001l3I-1dUj for pgsql-general@lists.postgresql.org; Mon, 09 Mar 2026 07:18:29 +0000 Received: from sciurus.exwg.net (unknown [IPv6:2001:470:7120:1:826d:97ff:fe4b:c7af]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "sciurus.exwg.net", Issuer "R12" (not verified)) by smtp.burggraben.net (Postfix) with ESMTPS id 060B8C011E1; Mon, 9 Mar 2026 08:18:25 +0100 (CET) Received: by sciurus.exwg.net (Postfix, from userid 1000) id 6BE87433CD9F; Mon, 09 Mar 2026 08:18:25 +0100 (CET) Date: Mon, 9 Mar 2026 08:18:25 +0100 From: Christoph Moench-Tegeder To: Igor Korot Cc: "pgsql-generallists.postgresql.org" Subject: Re: CREATE TABLE fails Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/2.2.13 (2024-03-09) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk ## Igor Korot (ikorot01@gmail.com): > > It's available as a TABLE storage parameter, but you put it on the index > > definition (where it's not valid) - this could be a conceptual mistake > > or a misplaced right parenthesis. > > See the example on your linked page: > > https://www.postgresql.org/docs/16/sql-createtable.html#SQL-CREATETABLE-STORAGE-PARAMETERS:~:text=fill%20factor%20for%20both%20the%20table%20and%20its%20unique%20index > > Please check the PRIMARY KEY clause on that same linked page. > It says "Storage Parameters" are definitely supported there. As I wrote earlier: autovacuum_enabled is not a valid storage parameter for indexes. The exact sentence after the one you're refering to tells you that "Storage parameters for indexes are documented in CREATE INDEX" and autovacuum_enabled is not documented there - it's valid for tables only. (On the other hand, there are index storage parameters which are not available for tables - they might make no sense on a table or refer to specific index types only). Regards, Christoph -- Spare Space.